[
https://issues.apache.org/jira/browse/AXIOM-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062815#comment-13062815
]
Hudson commented on AXIOM-353:
------------------------------
Integrated in axis2-1.6 #62 (See [https://builds.apache.org/job/axis2-1.6/62/])
Merged a couple of changes to the 1.6 branch to take advantage of the API
introduced by AXIOM-353: r1085173,r1085931,r1088730,r1089225,r1094117.
veithen :
Files :
*
/axis/axis2/java/core/branches/1_6/modules/xmlbeans/src/org/apache/axis2/xmlbeans/XmlBeansXMLReader.java
*
/axis/axis2/java/core/branches/1_6/modules/adb/src/org/apache/axis2/databinding/ADBSOAPModelBuilder.java
*
/axis/axis2/java/core/branches/1_6/modules/xmlbeans/src/org/apache/axis2/xmlbeans/template/XmlbeansDatabindingTemplate.xsl
* /axis/axis2/java/core/branches/1_6
*
/axis/axis2/java/core/branches/1_6/modules/adb/test/org/apache/axis2/databinding/ADBSOAPModelBuilderTest.java
*
/axis/axis2/java/core/branches/1_6/modules/adb-codegen/test/org/apache/axis2/schema/AbstractTestCase.java
*
/axis/axis2/java/core/branches/1_6/modules/addressing/test/org/apache/axis2/handlers/addressing/AddressingOutHandlerTest.java
> Need a replacement for OMXMLBuilderFactory
> ------------------------------------------
>
> Key: AXIOM-353
> URL: https://issues.apache.org/jira/browse/AXIOM-353
> Project: Axiom
> Issue Type: Improvement
> Components: API
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Fix For: 1.2.13
>
>
> Historically, org.apache.axiom.om.impl.llom.factory.OMXMLBuilderFactory was
> used to create Axiom trees from XML documents (and there are still places in
> Axis2 where this is used). Unfortunately, this class is located in the wrong
> package and JAR (it is implementation independent but belongs to LLOM).
> Nowadays, the standard way to create an Axiom tree is to instantiate
> StAXOMBuilder or one of its subclasses directly. However, this is not optimal
> for two reasons:
> * It implies the assumption that every implementation of the Axiom API
> necessarily uses StAXOMBuilder. This means that an implementation doesn't
> have the freedom to provide its own builder implementation (e.g. in order to
> implement some special optimizations).
> * StAXOMBuilder belongs to a package which has "impl" in its name. This tends
> to blur the distinction between the public API and internal implementation
> classes.
> There should be an abstract API for creating builder instances. It should be
> defined in terms of interfaces (such as OMXMLParserWrapper). OMMetaFactory is
> a good candidate for this because it is already used to encapsulate an
> implementation of the Axiom API (there is one implementation of OMMetaFactory
> for LLOM and one for DOOM).
--
This message is automatically generated by JIRA.
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]
