Hi, yes I did, but there is another problem coming by using the JBIWrapper. It seems to me, that there is some missmatch in the JBI specifications interpretation of how to handle JBI-Wrappers within the NormalizedMessage. In other words, using the JBI-Wrapper option causes ServiceMix to provide this Wrapper to the components. The CXF component itself desires this wrapper. Therefore to satisfy this component I've to provide such a wrapper within the message, crated by another componten (in my case a bean component) and this means to me, that I've to write components wich are aware of the relation to other compontents following up in the message flow. These components aren't "independent" anymore! So on my opinion the JBI Wrapper stuff has to be transparent for any component and the bus itselb has to handle all the meta data concerns coming up with the wrapper.
Hope that a developer of servicemix will reply to this. Thanks a lot, Tobias tmi wrote: > > Hi Tobias, > > Have you played with the useJBIWrapper property in your CXF BC > configuration? I don't recall all details but I had to set it in the > folllowing example. > > <cxfbc:provider wsdl="classpath:person.wsdl" > locationURI="http://localhost:8192/PersonService/"; > endpoint="Person" > service="person:PersonService" > interfaceName="person:Person" > useJBIWrapper="true"> > </cxfbc:provider> > -- View this message in context: http://www.nabble.com/cxf-bc-soap-processing-tp17867502p18026104.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
