The cause of the problem is your remote Axis-based service returning a SOAP envelope that does not adhere to BP 1.1. The developerWorks article you referenced confirms this.
In the thread you mention, I confirmed that the part accessors should have a namespace associated with them. I said that because a sample SOAP envelope in WSDL 1.1 implied it: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> | <soapenv:Body> | <m:GetLastTradePriceResponse xmlns:m="Some-URI"> | <m:price>34.5</m:price> | </m:GetLastTradePriceResponse> | </soapenv:Body> | </soapenv:Envelope> Notice the part accessor m:price is bound to a namespace. While fixing the problem, I found BP 1.1 specifies that part accessors have no namespace associated with them. This must be why SOAP stacks that predate BP 1.1 (such as Axis 1.x) write part accessors bound to a namespace. I see two solutions: update the remote SOAP stack so that it produces BP-1.1 envelopes allow jBPM BPEL to read pre-BP-1.1 envelopes Please file a feature request in JIRA if the former is definitely not possible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999326#3999326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999326 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
