I'm also having the same problem, is this resolved? Thanks, Roozbeh
gnodet wrote: > > If you put the log level to DEBUG, you should see the content of the > message send to the jsr181. If this one is not null, but the received > java bean is, that means the message has not been successfully > unmarshaled. Unfortunately, XFire is not very verbose about that ... > It also depends on the data mapping you use (jaxb, xmlbeans, aegis ...) > > On 9/22/06, Vijay Masina <[EMAIL PROTECTED]> wrote: >> I am trying to send a http soap request to servicemix and route the >> request to a JSR181 component.The message gets sent to the JSR181 >> component but the service Implementation class recieves empty request >> object (all the values are null). In the log4j logs I have observed the >> message is sent to the http component and processed by the JSR181 >> component. >> >> What could be the reason for passing empty message to the service >> implementation class? >> >> >> Here is the configuration: >> >> <sm:activationSpec componentName="servicemix-http" >> service="rcig:httpBinding" destinationService="rcig:soapBinding"> >> <sm:component> >> <http:component> >> <http:configuration managed="true" /> >> <http:endpoints> >> <http:endpoint service="rcig:httpBinding" >> soap="true" >> endpoint="rcig:httpEndpoint" >> targetService="rcig:soapBinding" >> role="consumer" >> soapAction="doPrevalidation" >> >> locationURI="http://localhost/AddressQueries/"; >> >> defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; /> >> </http:endpoints> >> </http:component> >> </sm:component> >> </sm:activationSpec> >> >> >> <sm:activationSpec componentName="servicemix-soap" >> service="rcig:soapBinding"> >> <sm:component> >> <jsr181:component> >> <jsr181:endpoints> >> <jsr181:endpoint >> endpoint="rcig:soapEndpoint" >> service="rcig:soapBinding" >> interfaceName="http://rcig.net/AddressQueries"; >> serviceInterface="net.rcig.AddressQueriesImpl" >> pojo="#addressQueriesBean" >> style="document" >> /> >> </jsr181:endpoints> >> </jsr181:component> >> </sm:component> >> </sm:activationSpec> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/jsr181-component-null-input-data-tf2320028s12049.html#a7198340 Sent from the ServiceMix - User mailing list archive at Nabble.com.
