[
https://issues.apache.org/jira/browse/AXIOM-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266864#comment-13266864
]
Andreas Veithen commented on AXIOM-399:
---------------------------------------
A remaining issue is that for a SOAP envelope with a body that contains an
OMSourcedElement with unknown name, a call to SOAPEnvelope#hasFault() will
cause the expansion of that element. This means that the feature introduced in
this JIRA doesn't interact well with the optimizations described in AXIOM-282,
but this should be fixable.
> Allow creation of OMSourcedElements with unknown local name and namespace URI
> -----------------------------------------------------------------------------
>
> Key: AXIOM-399
> URL: https://issues.apache.org/jira/browse/AXIOM-399
> Project: Axiom
> Issue Type: Improvement
> Components: API
> Affects Versions: 1.2.12
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Priority: Minor
> Fix For: 1.2.14
>
>
> Axiom already supports creating OMSourceElement instances that determine the
> namespace prefix lazily (see AXIOM-334). There are also some use cases where
> it is difficult or impossible to determine the local name and namespace URI
> at the time of creation of the OMSourcedElement (see e.g. AXIS2-5158). For
> these use cases Axiom should allow creation of OMSourcedElements with unknown
> local name and namespace URI. Of course, the OMSourcedElement implementation
> would need to be modified such that this kind of the element is automatically
> expanded (and the local name/namespace URI updated) when a call is made to
> getLocalName(), getNamespace() or getQName().
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
