[
https://issues.apache.org/jira/browse/CXF-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida resolved CXF-4176.
------------------------------
Resolution: Fixed
Fix Version/s: 2.6
2.5.3
This patch preserves the namespace prefixes. More specifically, all non empty
prefixes are preserved. Empty prefixes are preserved except when the outbound
transformer explicitly configures the default namespace to be changed (In this
case, the existing default namespace is assigned a new generated prefix).
In addition, another situation where a new prefix is generated is when an
unqualified element is promoted to be an qualified element (i.e., mapped to a
qualified element).
> preserve namespace prefixes in Transform Feature to support QName resolution
> for content
> ----------------------------------------------------------------------------------------
>
> Key: CXF-4176
> URL: https://issues.apache.org/jira/browse/CXF-4176
> Project: CXF
> Issue Type: Improvement
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Fix For: 2.5.3, 2.6
>
>
> Unless configured specifically otherwise (i.e., using the default namespace
> option to switch the default namespace), the original namespace prefixes
> should be preserved in the resulting XML document so that an element content
> typed as QName can be resolved against the namespace context.
> For example, if you have an input XML:
> <a:foo xmlns:a="urn:abc">
> <a2:bar xmlns:a2="urn:abc">a2:text</a2:bar>
> </a:foo>
> and suppose the content of element bar is of type QName.
> If we are transforming from {urn:abc}* to {urn:a}*, we should not
> simply generate:
> <a:foo xmlns:a="urn:a">
> <a:bar>a2:text</a:bar>
> </a:foo>
> Instead, we should generate:
> <a:foo xmlns:a="urn:a">
> <a2:bar xmlns:a2="urn:a">a2:text</a2:bar>
> </a:foo>
> so that the QName a2:text can be correctly interpreted.
> http://cxf.547215.n5.nabble.com/Transform-feature-to-preserve-prefix-values-Re-svn-commit-r1295714-tt5538162.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
