You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ws.apache.org by ve...@apache.org on 2017/05/13 13:50:28 UTC
svn commit: r1795063 - /webservices/axiom/trunk/src/site/apt/roadmap.apt
Author: veithen
Date: Sat May 13 13:50:28 2017
New Revision: 1795063
URL: http://svn.apache.org/viewvc?rev=1795063&view=rev
Log:
Update roadmap: the OMAttachmentAccessor interface has been repurposed and is no longer used in the way described in the roadmap.
Modified:
webservices/axiom/trunk/src/site/apt/roadmap.apt
Modified: webservices/axiom/trunk/src/site/apt/roadmap.apt
URL: http://svn.apache.org/viewvc/webservices/axiom/trunk/src/site/apt/roadmap.apt?rev=1795063&r1=1795062&r2=1795063&view=diff
==============================================================================
--- webservices/axiom/trunk/src/site/apt/roadmap.apt (original)
+++ webservices/axiom/trunk/src/site/apt/roadmap.apt Sat May 13 13:50:28 2017
@@ -83,33 +83,6 @@ Removal of unnecessary or irrelevant API
This section identifies APIs that have become unnecessary or irrelevant. Note that APIs that
have already been deprecated in 1.2.x (and will be removed in 1.3 anyway) are not listed here.
-* <<<org.apache.axiom.om.OMAttachmentAccessor>>>
-
- In Axiom versions prior to 1.2.9, the sequence of events produced by the <<<XMLStreamReader>>>
- returned by <<<getXMLStreamReaderWithoutCaching>>> was inconsistent if the underlying stream is
- XOP encoded (see AXIOM-255). This made it necessary for application code to (partially) handle the
- XOP processing itself. That is the reason why the <<<XMLStreamReader>>> instance (which is
- an <<<OMStAXWrapper>>>) implements <<<OMAttachmentAccessor>>>: it allowed the application code
- to retrieve the binary content for undecoded <<<xop:Include>>> elements.
-
- Starting with Axiom 1.2.9 the sequence of events produced by the
- <<<XMLStreamReader>>> is always the same (i.e. XOP is always completely decoded) and all binary
- content is reported through the <<<DataHandlerReader>>> extension, making the <<<OMAttachmentAccessor>>>
- API unnecessary in that context.
-
- The interface is used in several other contexts as well, but it is actually unnecessary in each of them:
-
- * The <<<Attachments>>> class implements <<<OMAttachmentAccessor>>>. However, it is not possible to
- substitute an <<<Attachments>>> object by an arbitrary <<<OMAttachmentAccessor>>> instance (e.g. when
- parsing an XOP/MTOM message). This would actually be a useful feature, but in that particular context,
- there is an overlap with the <<<MimePartProvider>>> interface and that API would be better suited.
-
- * The <<<OMAttachmentAccessor>>> API is required in conjunction with the <<<setInlineMTOM>>> method
- defined by <<<OMXMLStreamReader>>>. However, that method is deprecated.
-
- * The <<<XOPBuilder>>> interface extends <<<OMAttachmentAccessor>>>. However, as explained below,
- that API will be removed in Axiom 1.3.
-
* <<<org.apache.axiom.om.impl.builder.XOPBuilder>>>
The <<<XOPBuilder>>> interface is implemented by <<<XOPAwareStAXOMBuilder>>> and <<<MTOMStAXSOAPModelBuilder>>>.