[
https://issues.apache.org/jira/browse/CXF-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531063#comment-14531063
]
Akitoshi Yoshida commented on CXF-6394:
---------------------------------------
[~dkulp],
Hi Dan,
I think the node creation option doesn't look good because you then need to
create the entire node or a partial one, and keep it in the message and later
traverse it over to get the namespace decls.
I think it's simpler to just create a map when this option is enabled in the
context properties.
I'll submit the change shortly.
regards, aki
> Add an option to add the namespace map of the container element in the message
> ------------------------------------------------------------------------------
>
> Key: CXF-6394
> URL: https://issues.apache.org/jira/browse/CXF-6394
> Project: CXF
> Issue Type: Improvement
> Components: Soap Binding
> Affects Versions: 3.0.5
> Reporter: Akitoshi Yoshida
> Assignee: Akitoshi Yoshida
>
> When there is no DOM node is created during the inbound SOAP message
> processing, the body child is represented by the Source object.
> It seems reasonable to add an option to create a map containing the namespace
> declarations during the SOAP envelope parsing and put it in the message so
> that one can directly access this map later in their application (e.g. in
> camel-cxf).
> This behavior is related to the recent versions of CXF which no longer create
> a DOM node by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
