[jboss-jira] [JBoss JIRA] (AS7-3768) Unexpected failure for WS-Addressing tests

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669729#comment-12669729 ] 

Alessio Soldano edited comment on AS7-3768 at 2/21/12 4:20 PM:
---------------------------------------------------------------

I *think* you're right, you're dealing with a caching issue, more specifically you're probably ending up using the same Apache CXF bus instance on client side and the client in there is named with the name of service it relates to. A cxf specific way of avoiding this is to  force creating a new instance of CXF Bus for each test (that of course affects performances). So there's basically a solution for users having clients consuming multiple services with the same qualified name in the same client thread (not that common situation after all anyway). The jbossws doc warns about potential issues with bus association to the current thread, especially when running in-container (https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration); this is design choice of Apache CXF in any case.
                
      was (Author: asoldano):
    I *think* you're right, you're dealing with a caching issue, more specifically you're probably ending up using the same Apache CXF bus instance on client side and the client in there is named with the name of service is relates to. A cxf specific way of avoiding this is to  force creating a new instance of CXF Bus for each test (that of course affects performances). So there's basically a solution for users having clients consuming multiple services with the same qualified name in the same client thread (not that common situation after all anyway). The jbossws doc warns about potential issues with bus association to the current thread, especially when running in-container (https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration); this is design choice of Apache CXF in any case.
                  
> Unexpected failure for WS-Addressing tests
> ------------------------------------------
>
>                 Key: AS7-3768
>                 URL: https://issues.jboss.org/browse/AS7-3768
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Web Services
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Rostislav Svoboda
>            Assignee: Richard Opalka
>              Labels: eap6_LA
>
> I'm developing WS-Addressing tests for AS7 TS and I hit interesting issue.
> It's about org.jboss.as.test.integration.ws.wsa.TestNoAddressingTestCase -- usingWSDLFromDeployedEndpoint test, when I run just TestNoAddressingTestCase everything if fine, but when I run all Test*AddressingTestCase I have failure.
> Main error message is 'A required header representing a Message Addressing Property is not present{http://www.w3.org/2005/08/addressing}MessageAddressingHeaderRequired'. But WS-Addressing shouldn't be enabled at all.
> Just TestNoAddressingTestCase (./integration-tests.sh -e -Dts.basic clean test -Dtest=TestNoAddressingTestCase)
> Details for usingWSDLFromDeployedEndpoint (@HandlerChain used to dump message)
> {code}
> -----------
> Incoming message:
> -----------
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header/><soap:Body><ns2:sayHello xmlns:ns2="http://www.jboss.org/jbossws/ws-extensions/wsaddressing"><arg0>no-addressing</arg0></ns2:sayHello></soap:Body></soap:Envelope>
> -----------
> Outgoing message:
> -----------
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:sayHelloResponse xmlns:ns2="http://www.jboss.org/jbossws/ws-extensions/wsaddressing"><return>Hello no-addressing!</return></ns2:sayHelloResponse></soap:Body></soap:Envelope>
> -----------
> {code}
> All Test*AddressingTestCase (./integration-tests.sh -Dts.basic clean test -Dtest=Test*AddressingTestCase)
> Details for usingWSDLFromDeployedEndpoint:
> {code}
> -----------
> Incoming message:
> -----------
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">http://www.jboss.org/jbossws/ws-extensions/wsaddressing/ServiceIface/sayHello</Action><MessageID xmlns="http://www.w3.org/2005/08addressing">urn:uuide4f20e7-e3d3-4e04-a4fc-c1830ca2c9e8</MessageID><To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/jaxws-wsa/AddressingService</To><ReplyTo xmlns="http://www.w3.org/2005/08/addressing"><Address>http://www.w3.org/2005/08/addressing/anonymous</Address></ReplyTo></soap:Header><soap:Body><ns2:sayHello xmlns:ns2="http://www.jboss.org/jbossws/ws-extensions/wsaddressing"><arg0>no-addressing</arg0></ns2:sayHello></soap:Body></soap:Envelope>
> -----------
> Outgoing message:
> -----------
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:sayHelloResponse xmlns:ns2="http://www.jboss.org/jbossws/ws-extensions/wsaddressing"><return>Hello no-addressing!</return></ns2:sayHelloResponse></soap:Body></soap:Envelope>
> -----------
> {code}
> Details:
>  - How could addressing appear in incoming message?
>  - I dump generated WSDL file and it contains no addressing namespaces and elements [1]
>  - I think WS lookup in usingWSDLFromDeployedEndpoint method is just standard
>  - Is there any client side caching? TestNoAddressingTestCase must be influenced by other tests.
> Branch with WS-Addressing tests:  https://github.com/rsvoboda/jboss-as/tree/ws-addressing
> Commit: https://github.com/rsvoboda/jboss-as/commit/c345ea0ebccb50bdbada5cd105d2fccf83e09015
> [1] WSDL dump: https://github.com/rsvoboda/jboss-as/commit/c345ea0ebccb50bdbada5cd105d2fccf83e09015#L7R103

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira