You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "onder sezgin (JIRA)" <ji...@apache.org> on 2017/01/25 07:27:26 UTC
[jira] [Commented] (CAMEL-5980) camel-mail - Better handle null
values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837313#comment-15837313 ]
onder sezgin commented on CAMEL-5980:
-------------------------------------
Hi, I am trying to reproduce the issue,
when i ran the junit case on windows, i see error as below;
java.lang.AssertionError: expected null, but was:<org.apache.camel.component.direct.DirectConsumerNotAvailableException: No consumers available on endpoint: direct://email-file. Exchange[ID-TT10772507-58856-1485328987571-1-2]>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at org.apache.camel.component.mail.EmailExceptionTest.testEmailFileNew(EmailExceptionTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
then i changed the consuming endpoint as below;
{code}
template.send("log:logging?level=WARN&showAll=true", exchange);
{code}
then there is no error.
however, when i ran junit test case on mac(unix), i got the error as Axel mentioned.
I am not sure if this is really a problem.
> camel-mail - Better handle null values when extracting attachments
> ------------------------------------------------------------------
>
> Key: CAMEL-5980
> URL: https://issues.apache.org/jira/browse/CAMEL-5980
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
> Affects Versions: 2.9.0, 2.10.0
> Reporter: Claus Ibsen
> Assignee: onder sezgin
> Priority: Minor
> Fix For: Future
>
> Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, EmailExceptionTest.java, EmailTest.java, Exception Mail.eml
>
>
> See nabble
> http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html
> We should see if we can fix the Camel code to handle those null data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)