[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3176) JbossWS native client handler issue

[Alessio Soldano (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3176:
----------------------------------

    Fix Version/s: jbossws-native-4.0


> JbossWS native client handler issue
> -----------------------------------
>
>                 Key: JBWS-3176
>                 URL: https://issues.jboss.org/browse/JBWS-3176
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.2.2
>         Environment: RiftSaw 2.2.0.CR1, JBossAS 5.1.0.GA, JBossWS 3.2.2.GA (installed as part of the RiftSaw installation), JBossESB 4.9, JDK6, Savara 1.1.0.CR1
>            Reporter: Gary Brown
>             Fix For: jbossws-native-4.0
>
>         Attachments: CreditCheckServiceEAR.ear, DrivingRecordServiceEAR.ear, policyquote-queue-service.xml, PolicyQuoteCalculationService.esb, PolicyQuoteEntityService.esb, PolicyQuoteEntitySLSBEAR.ear, PolicyQuoteProcess-PolicyQuoteProcessService.jar
>
>
> I have a BPEL process that invokes two JAX-WS services, one after the other. The first invocation does not trigger the client handler configured in the 'standard-jaxws-client-config.xml' file, however the second invocation does.
> In terms of the environment, when you have a clean JBossAS environment, install the ESB, install Riftsaw using "ant deploy -Ddatabase=hsql -Dws.version=3.2.2.GA" (which will install jbossws native 3.2.2.GA).
> For now don't worry about installing Savara, as it is only configuring the client handler. May be easier for you to use your own handler, rather than installing yet another project - although if you have problems reproducing the issue, then may need to install Savara in case that is the problem.
> Attached are the various artifacts that need to be deployed into the server's deploy folder. The policy-quote-queue-service.xml will need to be deployed first.
> SoapUI can be used to send the following messages. The instructions for running the example are:
> 1) Send
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pol="http://www.example.org/policyQuote">
>    <soapenv:Header/>
>    <soapenv:Body>
>       <pol:policyQuote>
>   <pol:receivePolicyQuote>
>          <pol:requestDate>2009-01-01</pol:requestDate>
>             <pol:task>receivePolicyQuote</pol:task>
>             <pol:policyQuoteInfo>
>                 <pol:policyType>AUTO</pol:policyType>
>                 <pol:vehicleYear>2004</pol:vehicleYear>
>                 <pol:driverName>Bill Smith</pol:driverName>
>                  <pol:ssn>412345678</pol:ssn>
>                  <pol:dlNumber>987654321</pol:dlNumber>
>                  <pol:age>30</pol:age>
>                   <pol:numberOfAccidents>0</pol:numberOfAccidents>
>                   <pol:numberOfTickets>0</pol:numberOfTickets>
>              <pol:creditScore>0</pol:creditScore>
>               <pol:price>0</pol:price>
>     </pol:policyQuoteInfo>
>   </pol:receivePolicyQuote>
>       </pol:policyQuote>
>    </soapenv:Body>
> </soapenv:Envelope>
> to this URL
> http://localhost:8080/PolicyQuoteProcessServiceService/PolicyQuoteProcessServicePort
> 2) Then wait until you see the following on the console:
> Received Driving Record Request for: Bill Smith
> 3) Then send:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:drv="http://dmv.com/drivingRecord">
>    <soapenv:Header/>
>    <soapenv:Body>
>       <drv:drivingRecordResponse>
>        <drv:name>Bill Smith</drv:name>
>         <drv:ssn>412345678</drv:ssn>
>         <drv:dlNumber>987654321</drv:dlNumber>
>         <drv:age>30</drv:age>
>         <drv:numberOfTickets>2</drv:numberOfTickets>
>         <drv:numberOfAccidents>1</drv:numberOfAccidents>
> </drv:drivingRecordResponse>
>    </soapenv:Body>
> </soapenv:Envelope>
> to
> http://localhost:8080/PolicyQuoteProcessServiceService/DrivingRecordCallbackServicePort
> (The example has been provided by Jeff DeLong).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira