ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbi joe <...@daggerpoint.net>
Subject Re: Servicemix mapper with soap Message
Date Wed, 02 Jan 2008 19:04:20 GMT

Yes, passed in and outa BPEL and other Assemblies.
I think I figured out what the problem was.
Looks like my WSDL needs a element name in the
XML schema that is inside the Soap message. 
After adding the Element name to the WSDL
I am now able to get past the line of code 
I have referenced.  However, Im getting duplicate
XML messages out of the ODE engine.  Again,
Im sure its something IM doing wrong.  

XGuy wrote:
> Is this SOAP message something that you would pass into a business process
> or something?
> jbi joe wrote:
>> I have created a soap message, it fails. 
>> I posted a snippet of it on this list previously.
>> Im using a MessageFactory to create a very easy soap message, using
>> java Service Assembly.  Never gets to BPEL Processing.
>> I tracked it into code and here is where it gows goodby.
>> I printerd out all the values that are being looked at here and most are
>> empty.
>> Can someone tell my how to fix it?
>>                     foiled by the following line in
>> ServicemixMapper.java;
>>  // servicemix-http has a (bad) habit of placing the SOAP body content
>> directly in the normalized message
>>             QName elementName = part.getElementName();
>>             if (elementName != null &&
>> elementName.getLocalPart().equals(msg.getLocalName())
>>                     &&
>> elementName.getNamespaceURI().equals(msg.getNamespaceURI())) {
>>                 pdata = msg;
>>             }

View this message in context: http://www.nabble.com/Servicemix-mapper-with-soap-Message-tp14507250p14584111.html
Sent from the Apache Ode User mailing list archive at Nabble.com.

View raw message