[
https://issues.apache.org/jira/browse/WSCOMMONS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved WSCOMMONS-258.
--------------------------------------
Resolution: Fixed
Committed revision 584195.
> SOAPHeaderBlock that is an OMSourcedElement
> -------------------------------------------
>
> Key: WSCOMMONS-258
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-258
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> The improvements to OMSourcedElement (and OMDataSource) make it very easy to
> use other kinds of objects for the data payload.
> Problem:
> In some scenarios, I want to do the same thing for the elements inside a
> SOAPHeader.
> However, the elements in a SOAPHeader are SOAPHeaderBlock elements. They are
> not OMSourcedElements.
> Possible Scenario:
> It would be convenient to put an EndpointReference object (or other WSA
> objects) directly into the OM SOAPHeader.
> This would have the same benefits as an OMSourcedElement in the payload (i.e.
> smaller footprint, delayed expansion, convenient objects).
> Solution:
> Change SOAPHeaderBlock to implement OMSourcedElement.
> This also has the side effect of showing how to extend OMSourcedElement for
> other uses.
> I have the code working and I am in the middle of testing. I intend to
> commit the code and test on Friday.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
