cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bozhong Lin (JIRA)" <j...@apache.org>
Subject [jira] Closed: (CXF-289) Adding of Root Node in XMLBinding is done without a prefix.
Date Wed, 06 Dec 2006 10:43:23 GMT
     [ http://issues.apache.org/jira/browse/CXF-289?page=all ]

Bozhong Lin closed CXF-289.
---------------------------

    Resolution: Fixed

> Adding of Root Node in XMLBinding is done without a prefix.
> -----------------------------------------------------------
>
>                 Key: CXF-289
>                 URL: http://issues.apache.org/jira/browse/CXF-289
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0-RC
>            Reporter: Ajay Paibir
>         Assigned To: tli
>            Priority: Minor
>             Fix For: 2.0-RC
>
>         Attachments: XMLMessageOutInterceptor.java
>
>
> in XMLMessageOutInterceptor the xmlformat RootNode if present is added without a suitable
prefix. This causes the rootNode element to be in xmlns="some namespace uri" whichis okay.
But some child elements end up in this namespace since they are not qualified.
> A typical XMLMessage generated for soap_header.wsdl in testutil. is 
> <inHeaderReqNode xmlns="http://apache.org/headers">
>      <inHeader xmlns:ns2="http://www.w3.org/2005/08/addressing/wsdl" xmlns="http://apache.org/headers/types">
>         <requestType>in request type</requestType>
>      </inHeader>
>      <SOAPHeaderInfo xmlns:ns2="http://www.w3.org/2005/08/addressing/wsdl" xmlns="http://apache.org/headers/types">
>          <originator>in originator</originator>
>          <message>in message</message>
>      </SOAPHeaderInfo>
> </inHeaderReqNode>
> So the <requestType> elements should be in http://apache.org/headers/types but
actually end up in http://apache.org/headers.
> The fix for this in XMLMessageOutInterceptors which is attached with this bug description.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message