cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-1291) Create an interceptor to strip XML namespaces....
Date Fri, 27 May 2011 14:24:47 GMT


Sergey Beryozkin commented on CXF-1291:

Christian, elementFormDefault='unqualified' does not imply that is is a default namespace
which is used.
Having elementFormDefault='unqualified' and say <a xmlns="http://bar><b/></a>
won't work, at least for stacks enforcing elementFormDefault='unqualified', because b is qualified.

<ns:a xmlns:ns="http://bar><b/></ns:a>
<a xmlns="http://bar><b xmlns=""/></ns:a>
is correct. 

For some people this means <b/> is in the global scope, for others that <b/> is
local to its parent ns:a element. I'm in the latter camp. There was an article about
it, plenty of refs, check 'Martin Gudgin elementFormDefault'.  

> Create an interceptor to strip XML namespaces....
> -------------------------------------------------
>                 Key: CXF-1291
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0.3
>            Reporter: Daniel Kulp
>            Assignee: Sergey Beryozkin
> A couple of folks on cxf-user have asked for the ability to return XML with all the namespaces
completely stripped out.   
> An "interesting" approach could be to add an interceptor immediately after the StaxOutInterceptor
that would wrapper the  XMLStreamWriter with a writer that would discard all namespace related
events.  We just need the interceptor to be created.   Adding it can be a configuration item
for the user.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message