You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by jbi joe <jo...@daggerpoint.net> on 2007/12/26 23:34:30 UTC
Servicemix mapper with soap Message
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-tp14507250p14507250.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Servicemix mapper with soap Message
Posted by jbi joe <jo...@daggerpoint.net>.
I am sending a XML soap envelope from a
java based Service Assmbly to an Endpoint that happens
to be a BPEL Assembly, then from the BPEL SA to many
other BPEL SA's and also many other JAVA SA's. ALl the
Java Service Asssmblies are connected to the LW-Container
of Servicemix. Way too much code to post.
XGuy wrote:
>
> Was it a JMS on SOAP message?
>
> Can I try this one out (only if it is ok with you).
> Maybe I could help figure out what is going on.
>
>
>
> Can I try out the sample on my machine? I am trying to get a
>
> jbi joe wrote:
>>
>> 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-tp14507250p14594028.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Servicemix mapper with soap Message
Posted by XGuy <il...@yahoo.com>.
Was it a JMS on SOAP message?
Can I try this one out (only if it is ok with you).
Maybe I could help figure out what is going on.
Can I try out the sample on my machine? I am trying to get a
jbi joe wrote:
>
> 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-tp14507250p14584312.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Servicemix mapper with soap Message
Posted by XGuy <il...@yahoo.com>.
Sorry about the message that appears half-done. I could try this on my
machine and see if I can try my hand at it.
jbi joe wrote:
>
> 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-tp14507250p14584841.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Servicemix mapper with soap Message
Posted by jbi joe <jo...@daggerpoint.net>.
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.
Re: Servicemix mapper with soap Message
Posted by XGuy <il...@yahoo.com>.
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-tp14507250p14583655.html
Sent from the Apache Ode User mailing list archive at Nabble.com.