[ https://jira.jboss.org/jira/browse/JBWS-2917?page=com.atlassian.jira.plug... ] Richard Opalka commented on JBWS-2917: -------------------------------------- Related issue: http://issues.apache.org/jira/browse/XALANJ-2382 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2917?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2917: --------------------------------- Description: JAXB internally uses JAXP API 1.3 (in our case endorsed java xalan) When I pass the following XML <?xml version='1.0' encoding='UTF-8'?> <EndpointReference xmlns='http://www.w3.org/2005/08/addressing'> <Address>http://localhost:8080/jaxws-endpointReference</Address> <Metadata wsdli:wsdlLocation='http://org.jboss.ws/endpointReference http://localhost:8080/jaxws-endpointReference?wsdl' xmlns:wsdli='http://www.w3.org/ns/wsdl-instance'> <wsam:InterfaceName xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata' xmlns:wsns='http://org.jboss.ws/endpointReference'>wsns:Endpoint</wsam:InterfaceName> <wsam:ServiceName EndpointName='HelloPort' xmlns='' xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata' xmlns:wsns='http://org.jboss.ws/endpointReference'>wsns:EndpointService</wsam:ServiceName> </Metadata> </EndpointReference> and process it with the following code: StreamSource source = new StreamSource(new StringReader(XML_SOURCE)); EndpointReference epRef = EndpointReference.readFrom(source); printXml(epRef.toString()); the output will be (should be identical) <?xml version='1.0' encoding='UTF-8'?> <EndpointReference xmlns='http://www.w3.org/2005/08/addressing'> <Address>http://localhost:8080/jaxws-endpointReference</Address> <Metadata wsdli:wsdlLocation='http://org.jboss.ws/endpointReference http://localhost:8080/jaxws-endpointReference?wsdl' xmlns:wsdli='http://www.w3.org/ns/wsdl-instance'> <wsam:InterfaceName xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'>wsn... <wsam:ServiceName EndpointName='HelloPort' xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'>wsn... </Metadata> </EndpointReference> As you can see xmlns:wsns namespace declaration is lost during the identity process :( was: JAXB internally uses XALAN. When I pass the following XML <?xml version='1.0' encoding='UTF-8'?> <EndpointReference xmlns='http://www.w3.org/2005/08/addressing'> <Address>http://localhost:8080/jaxws-endpointReference</Address> <Metadata wsdli:wsdlLocation='http://org.jboss.ws/endpointReference http://localhost:8080/jaxws-endpointReference?wsdl' xmlns:wsdli='http://www.w3.org/ns/wsdl-instance'> <wsam:InterfaceName xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata' xmlns:wsns='http://org.jboss.ws/endpointReference'>wsns:Endpoint</wsam:InterfaceName> <wsam:ServiceName EndpointName='HelloPort' xmlns='' xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata' xmlns:wsns='http://org.jboss.ws/endpointReference'>wsns:EndpointService</wsam:ServiceName> </Metadata> </EndpointReference> and process it with the following code: StreamSource source = new StreamSource(new StringReader(XML_SOURCE)); EndpointReference epRef = EndpointReference.readFrom(source); printXml(epRef.toString()); the output will be (should be identical) <?xml version='1.0' encoding='UTF-8'?> <EndpointReference xmlns='http://www.w3.org/2005/08/addressing'> <Address>http://localhost:8080/jaxws-endpointReference</Address> <Metadata wsdli:wsdlLocation='http://org.jboss.ws/endpointReference http://localhost:8080/jaxws-endpointReference?wsdl' xmlns:wsdli='http://www.w3.org/ns/wsdl-instance'> <wsam:InterfaceName xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'>wsn... <wsam:ServiceName EndpointName='HelloPort' xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'>wsn... </Metadata> </EndpointReference> As you can see xmlns:wsns namespace declaration is lost during the identity process :( -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2917?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2917: --------------------------------- JBoss Forum Reference: http://community.jboss.org/message/524324#524324 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2917?page=com.atlassian.jira.plug... ] Richard Opalka commented on JBWS-2917: -------------------------------------- See http://issues.apache.org/jira/browse/XALANJ-2382 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWS-2917?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2917: --------------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira