David Ward created SWITCHYARD-710:
-------------------------------------
Summary: Allow direct storage of XML Nodes as Context properties from
ContextMappers
Key: SWITCHYARD-710
URL:
https://issues.jboss.org/browse/SWITCHYARD-710
Project: SwitchYard
Issue Type: Enhancement
Components: component-soap, core, docs
Affects Versions: 0.3, 0.4
Reporter: David Ward
Assignee: David Ward
Fix For: 0.5
What started as a discussion regarding the behavior of SOAPContextMapper I believe should
be a broader-scoped enhancement to ContextMappers in general.
Right now, soap header elements are being deconstructed by using their name as the context
property key, and their string value as the context property value. This does not take
into consideration more complex use cases such as when an entire XML (sub-)tree needs to
be stored for things like xml TX/security propagation, as required by SWITCHYARD-703.
Thus a configuration property on <contextMapper/> should be added so that the entire
Node can be carried along as-is.
I do believe that the default behavior, however, should be kept as it is now, since for
most cases I think just a simple value is sufficient.
How is this a bigger issue than SOAPContextMappers? Well, we need to go through the other
implementations to make sure values won't be assumed as simple Strings all the time.
One thing I noticed right away is the HornetQContextMapper, which gets values out using
source.getStringProperty instead of getObjectProperty. We need consistency across the
ContextMappers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira