[
https://issues.apache.org/jira/browse/AXIOM-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267046#comment-13267046
]
Hudson commented on AXIOM-399:
------------------------------
Integrated in ws-axiom-trunk #932 (See
[https://builds.apache.org/job/ws-axiom-trunk/932/])
AXIOM-399: Also support creation of OMSourcedElements with unknown prefix
(but known local name and namespace URI) through the OMFactory API. This
provides a more consistent alternative to AXIOM-334. In fact, with the "lossy
prefix" feature introduced by AXIOM-334, some part of the knowledge (the local
name and namespace URI) is provided through the OMFactory API while another
piece of information (the fact that the prefix is unknown) is provided through
a property set on the OMDataSource. This is not very consistent. (Revision
1333227)
Result = ABORTED
veithen :
Files :
*
/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/OMFactory.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/ds/custombuilder/ByteArrayCustomBuilder.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMSourcedElementImpl.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/java/org/apache/axiom/ts/om/sourcedelement/OMSourcedElementVariant.java
> 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: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
