cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-597) Adding the WS-A classes to the JAXBContext in JAXBDataBinding causes extra namespace to be written
Date Tue, 24 Apr 2007 21:58:15 GMT
Adding the WS-A classes to the JAXBContext in JAXBDataBinding causes extra namespace to be
written
--------------------------------------------------------------------------------------------------

                 Key: CXF-597
                 URL: https://issues.apache.org/jira/browse/CXF-597
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.0-RC
            Reporter: Dan Diephouse
             Fix For: 2.0


>From the mailing list:


Lately I am noticing some strange behavior.  Many of my responses have
xmlns="http://www.w3.org/2005/08/addressing/wsdl" at the root element
under the body, even though the response does not use the WS-Addressing.

Example Response:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
   <ns2:MyOperationResponse
xmlns:ns2="http://company.com/service/types"
xmlns="http://www.w3.org/2005/08/addressing/wsdl">
     <ns2:first>Chris</ns:first>
     <ns2:last>Moesel</ns2:last>
   </ns2: MyOperationResponse >
 </soap:Body>
</soap:Envelope>

Sometimes, however, this strange behavior does NOT occur.  The most
consistent way I have replicated it is by doing a clean install of my
app, jetty:run-war, and then make sure the first request is MTOM
enabled.

Also of note is that when the addressing NS is *not* the default NS (As
described above) it still is often defined as another NS with an alias
(even though it's never used).


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message