[esb-issues] [JBoss JIRA] Commented: (JBESB-1005) Field not populated when calling web service from SOAPProcessor

Tom Fennelly (JIRA) jira-events at lists.jboss.org
Tue Sep 11 13:03:23 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBESB-1005?page=comments#action_12376229 ] 
            
Tom Fennelly commented on JBESB-1005:
-------------------------------------

The issue for the ShippingRequest was that the SOAP request coming from the BPEL process had an error wrt to namespacing on orderNumber, which resulted in JBossWS container not unmarshaling that part of the message.  

Rather than modify the BPEL process, I fixed this from within the ESB by adding a transform on the SOAP request to fix the namespacing issue.

Commited at rev 15018.

> Field not populated when calling web service from SOAPProcessor
> ---------------------------------------------------------------
>
>                 Key: JBESB-1005
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1005
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Examples, Web Services
>    Affects Versions: 4.2
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Fennelly
>            Priority: Minor
>             Fix For: 4.2.1 IR1
>
>
> In QS webservice_bpel there is shipping service invoked from BPEL processor.  The BPEL processor sends correct SOAP request but ShippingRequest class do not have orderNumber field populated although it is present in the message.
> The request
> <aeaaanstmp0:customerNumber xmlns:aeaaanstmp0="http://org.jboss.esb/quickstarts/bpel/ABI_Shipping" xmlns:aetgt="http://org.jboss.esb/quickstarts/bpel/ABI_OrderManager" xmlns:ns="http://org.jboss.esb/quickstarts/bpel/ABI_OrderManager" xmlns:ns1="http://ordermanagement.activebpel.com/jaws" xmlns:std="http://schemas.active-endpoints.com/sample/standardtypes/2006/04/StandardTypes.xsd">123456</aeaaanstmp0:customerNumber>   <ns:orderNumber xmlns:ns1="http://org.jboss.esb/quickstarts/bpel/ABI_OrderManager">813a3682-f98e-4c97-a01e-ded0146b8cbf</ns:orderNumber>   <aeaaanstmp0:poNumber xmlns:aeaaanstmp0="http://org.jboss.esb/quickstarts/bpel/ABI_Shipping" xmlns:aetgt="http://org.jboss.esb/quickstarts/bpel/ABI_OrderManager" xmlns:ns="http://org.jboss.esb/quickstarts/bpel/ABI_OrderManager" xmlns:ns1="http://ordermanagement.activebpel.com/jaws" xmlns:std="http://schemas.active-endpoints.com/sample/standardtypes/2006/04/StandardTypes.xsd">PO000123</aeaaanstmp0:poNumber>
> converts to JavaBean
> ShippingRequest ( com.activebpel.shipping.ShippingRequest at af1c52c3    customerNumber = 123456    poNumber = PO000123    orderNumber = null     )

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list