[
https://issues.apache.org/activemq/browse/SM-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40263
]
Ryan Moquin commented on SM-1087:
---------------------------------
I forgot that there is a servicemix-http provider declaration that allows for
the use of useJBIWrapper, but it appears to choke on JBI wrapped messages sent
from the cxfse proxy component. When I send a message to a regular
servicemix-http component (the default one) the JBI wrapped message is
forwarded out, but when I use the soap-provider one, then I end up with a NPE.
I don't have the stack trace handy, but I'll try to get some time to day to
grab it and put it on here.
> Servicemix-http provider should unwrap JBI messages before sending them to
> the target URI
> -----------------------------------------------------------------------------------------
>
> Key: SM-1087
> URL: https://issues.apache.org/activemq/browse/SM-1087
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http
> Affects Versions: 3.2
> Environment: Windows XP, Servicemix 3.2
> Reporter: Ryan Moquin
>
> When using the cxfse proxy to a servicemix-http provider, the provider will
> sent off requests in the exact form it gets them (it appears). Since the cxf
> se proxy, can only communicate to an internal component, it always wraps it's
> communications in a JBI wrapper. This means that a receiving http provider
> will then forward the JBI message is is, to the targetURI which will cause a
> failure on that target server. Servicemix-http should remove this wrapper
> before sending.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
