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

[Richard Opalka (JIRA)]

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

Richard Opalka resolved AS7-3768.
---------------------------------

    Resolution: Rejected


<ropalka> rsvoboda, Yes, it seems there will be caches applied.
<ropalka> rsvoboda, They will be there to speed up the client execution.
<ropalka> rsvoboda, I'd suggest in this specific use case to use different service names for each test.
<ropalka> rsvoboda, in order to avoid this caching problem
<rsvoboda> ropalka, I use the same serviceName and portName for all 3 endpoints
<ropalka> rsvoboda, would it be a big problem for you?
<ropalka> rsvoboda, yes, this will be that caching issue IMO
<ropalka> rsvoboda, I can debug it but I think your idea is right - there will be some caches applied
<rsvoboda> ropalka, can it be problem for end user?
<ropalka> rsvoboda, I don't think so. In real world each service should have unique service name
<rsvoboda> ropalka, it's in 'ideal world'
<ropalka> rsvoboda, exactly
<ropalka> rsvoboda, and world isn't perfect
<ropalka> rsvoboda, but I don't think it's a problem. 
<ropalka> rsvoboda, if I'd debug it, I'd probably found that cache
<ropalka> rsvoboda, and would implement system property for disabling it (if it's not implemented yet)
<ropalka> rsvoboda, but it would slow down WS clients significantly IMO
<ropalka> rsvoboda, and we prefer speed over correctness in this case
<ropalka> rsvoboda, so I recommend to rename services to be unique for each test :D
<ropalka> rsvoboda, or execute each test in different JVM
<rsvoboda> ropalka, well, caching would be by default enabled and disabled only on request ... but I'll rework my tests to use different names
<ropalka> rsvoboda, thanks
                
> 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
>             Fix For: 7.1.1.Final
>
>
> 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