Closed glassfishrobot closed 13 years ago
Reported by jfdenise@java.net
jfdenise@java.net said: I meant wsa:faulTo.
jfdenise@java.net said: Actually it applies to both faultTo and replyTo.
jfdenise@java.net said:
In addition, if the element contained in the referencecParameters is of type
QName, the namespace of its value must also be declared.
EG:
jitu@java.net said: Assigning it to Rama
ramapulavarthi@java.net said: Can you attach a test case with environment details. I tried to reproduce the issue but could n't. Is your server Provider, if so which type? Also is your service implementation throwing the exception? A test case would help me quickly reproduce the problem. Thanks.
jfdenise@java.net said: This is very difficult to extract . We are in a very specific context. I can provide you with the request that is sent by the client. The server is a provider annotated as follow : @WebServiceProvider() @ServiceMode(value=Service.Mode.MESSAGE) @BindingType(value=SOAPBinding.SOAP12HTTP_BINDING) @MemberSubmissionAddressing(required=false) public class JMXWSManServiceEndpoint
The client request :
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:user="http://foo.bar" xmlns:xs="http://www.w3.org/2001/XMLSchema">
scm_issue_link@java.net said: Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-unit/testcases/epr/issue564/test.bsh (1.1) /jax-ws-sources/jaxws-unit/testcases/epr/issue564/test-descriptor.xml (1.1) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20080703184131
Log: JAX-WS-564: Adding testcase for issue564
scm_issue_link@java.net said: Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-unit/testcases/epr/issue564/test1.bsh (1.1) /jax-ws-sources/jaxws-unit/testcases/epr/issue564/test-descriptor.xml (1.2) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20080703185825
Log: JAX-WS-564: Adding Stream Message testcase for issue564
scm_issue_link@java.net said: Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-unit/testcases/wsa/submission/fromwsdl/issue564/server/AddNumbers.wsdl (1.1) /jax-ws-sources/jaxws-unit/testcases/wsa/submission/fromwsdl/issue564/server/AddNumbersImpl.java (1.1) /jax-ws-sources/jaxws-unit/testcases/wsa/submission/fromwsdl/issue564/test-descriptor.xml (1.1) /jax-ws-sources/jaxws-unit/testcases/wsa/submission/fromwsdl/issue564/test.bsh (1.1) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20080703193439
Log: JAX-WS-564: Adding end to end WSA testcase for issue564
scm_issue_link@java.net said: Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/message/stream/StreamHeader.java (1.4) /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/StreamSOAPCodec.java (1.7) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20080814021810
Log: JAX-WS-564: A fix related to writing the inscope namespaces. This should fix StreamHeader.writeTo(). The fix for Reference Parameters in ReplyTo/FaultTo EPR is yet to be done and requires changes in Streambuffer impl or WSEndpointReference Impl.
ramapulavarthi@java.net said: This happens when the ns decalrations for the reference parameters is on top-level elements that the refereceparameter itself. WSEndpointReference is optimized using XmlStreamBuffer and xsb is not capturing the ns declarations on the parent and hence lost during the writing of same buffer as reference parameters in response.
The fix should be made in xmlstreambuffer or remove the use xsb for reference parameters.
Adding keyword metro2.0-waived as this is little uncommon case.
jitu@java.net said: Setting target milestone to 2.2.2
ramapulavarthi said: Either xsb needs to handle this or changing the WSEndpointReference implementation to not use xsb needs lot of changes and risky to change now. Waiving for this release.
ramapulavarthi said: Fixed in JAX-WS 2.2.6 with the integration of xmlstreambuffer 1.3 that has fixes for http://java.net/jira/browse/JAX_WS-957 http://java.net/jira/browse/JAX_WS-958
JAX-WS-957, JAX-WS-958: Integrating xmlstreambuffer 1.3 that has fixes for processing inscope namespaces when XMLStreamReader and SAXBufferProcessor is created from the buffer with inscope namespcaes.
branches/jaxws22/jaxws-ri/rt/src/com/sun/xml/ws/api/addressing/WSEndpointReference.java
Issue fixed in xsb 1.3, Fixing the tests to verify as per the differences in w3c and member versions
trunk/jaxws-unit/testcases/epr/issue564/test-descriptor.xml
snajper said: Marking as resolved based on latest comments.
Was assigned to ramapulavarthi
This issue was imported from java.net JIRA JAX_WS-564
Marked as fixed on Wednesday, November 9th 2011, 5:28:51 am
wsa:replyTo added ReferenceParameter elements namespace(s) declarations is(are) not added to the response.
Environment
Operating System: All Platform: Sun
Affected Versions
[2.1.4]