[
https://issues.apache.org/activemq/browse/CAMEL-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50824#action_50824
]
Claus Ibsen commented on CAMEL-1474:
------------------------------------
William
You need to fix the SMX side as well. You now get failure in SMX when running
Camel 2.0 trunk there:
{code}
13:41:14,211 | WARN | nerContainer-323 | DefaultMessageListenerContainer |
AbstractMessageListenerContainer 646 | Execution of JMS message listener
failed
java.lang.NoSuchMethodError:
org.apache.camel.spi.HeaderFilterStrategy.applyFilterToCamelHeaders(Ljava/lang/String;Ljava/lang/Object;)Z
at
org.apache.camel.component.mail.MailBinding.appendHeadersFromCamelMessage(MailBinding.java:126)
at
org.apache.camel.component.mail.MailBinding.populateMailMessage(MailBinding.java:82)
at
org.apache.camel.component.mail.MailProducer$1.prepare(MailProducer.java:48)
at
org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:354)
at
org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:346)
at
org.apache.camel.component.mail.MailProducer.process(MailProducer.java:46)
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:69)
at
org.apache.camel.processor.DelegateProcessor.processNext(DelegateProcessor.java:49)
at
org.apache.camel.processor.DelegateProcessor.proceed(DelegateProcessor.java:78)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:115)
at
org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:43)
{code}
> On the wire headers are dropped inside camel route between two CxfEndpoints
> ---------------------------------------------------------------------------
>
> Key: CAMEL-1474
> URL: https://issues.apache.org/activemq/browse/CAMEL-1474
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.6.0
> Reporter: Marat Bedretdinov
> Assignee: William Tam
> Fix For: 2.0.0, 1.6.1
>
> Attachments: camel-cxf-CAMEL-1474-2009-03-20.patch.txt
>
>
> Currently if there is a Camel route that involves two or more cxf endpoints,
> then the on the wire message headers such as SOAP headers are dropped.
> This fix enables one to relay these headers along the route or preserve the
> old behaviour and drop the headers.
> Headers relay/drop is bidirectional. Both out-of-band (*not* defined in WSDL
> contract) and in-band (defined in WSDL contract) headers are supported.
> Relaying headers can be further customized by implementing additional logic
> inside of MessageHeadersRelay interface.
> The default behaviour is to relay headers provided that an instance of
> MessageHeadersRelay bound to message binding namespace allows a header to be
> relayed.
> Please see
> .../components/camel-cxf/src/test/java/org/apache/camel/component/cxf/soap/headers/CxfMessageHeadersRelayTest.java
> for details on how this is done.
> Attached is the patch that provides this functionality.
> Thanks,
> Marat
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
