Mailing-List: contact announce-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of andreas.veithen@gmail.com
 designates 209.85.161.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:from:date:x-google-sender-auth:message-id
         :subject:to:content-type;
        b=ada4u/for4n7hXKAqa7kgZuDGcqYVfp6nxrpOuSBxSWSs2uar3VOC7d55rPYuTCnzW
         7AuJjFUfFj2KY3fPXBNX8JkRGaM3KWi8Vj6fKuyRbPxbyyl3PpOJoZpgq/vkd3yM/8c/
         QMb3vvDM4jV74oGLMXfh0VuqU3Sas83mnJd0E=
MIME-Version: 1.0
Sender: andreas.veithen@gmail.com
From: Andreas Veithen <veithen@apache.org>
Date: Mon, 12 Jul 2010 21:51:57 +0200
Message-ID: <AANLkTim1R0WxPDm90w4voh0CFGlh62WNhmf1oY3h_i42@mail.gmail.com>
Subject: [ANN] Axiom 1.2.9 released
To: announce@apache.org
Content-Type: text/plain; charset=ISO-8859-1

Apache Axiom Team is pleased to announce the release of Axiom 1.2.9.
The release is available for download at:

 http://ws.apache.org/commons/axiom/download.cgi

Apache Axiom is a StAX-based, XML Infoset compliant object model which
supports on-demand building of the object tree. It supports a novel
"pull-through" model which allows one to turn off the tree building
and directly access the underlying pull event stream. It also has
built in support for XML Optimized Packaging (XOP) and MTOM, the
combination of which allows XML to carry binary data efficiently and
in a transparent manner. The combination of these is an easy to use
API with a very high performant architecture!

Developed as part of Apache Axis2, Apache Axiom is the core of Apache
Axis2. However, it is a pure standalone XML Infoset model with novel
features and can be used independently of Apache Axis2.

Highlights in this release:

- Improved interoperability with StAX implementations other than
Woodstox. Axiom now detects the StAX implementation that is used and
works around interoperability issues. In particular, version 1.2.9
solves the longstanding concurrency issue that occurs when using Axiom
with SJSXP.
- Better control over XMLInputFactory and XMLOutputFactory settings.
It is now possible to use property files to define application wide
default settings for the StAX factories used by StAXUtils. It is also
possible to specify a particular configuration when requesting a StAX
parser from StAXUtils.
- Improved XOP/MTOM handling. Axiom 1.2.9 is able to stream
binary/base64 data in several situations where this was not possible
previously. The behavior of Axiom 1.2.9 is also more consistent with
respect to XOP encoded data sent to the application, solving some
issues where attachments were processed incorrectly.
- Improved documentation. There is now more and better Javadoc. Also,
a user guide is available in HTML and as PDF.
- Better OSGi support.
- Improved consistency of the core interfaces. E.g. OMDocument now has
a build method.

Resolved JIRA issues:

[WSCOMMONS-547] apache-release profile not working
[WSCOMMONS-546] axiom unit test failure in axiom-parser-tests
[WSCOMMONS-545] Legal issue related to inclusion of Jaxen source code in Axiom
[WSCOMMONS-541] Create replacement for UUIDGenerator
[WSCOMMONS-540] CustomBuilder interface is not well defined for
optimized binary data
[WSCOMMONS-536] OMStAXWrapper generated illegal event code of 0
[WSCOMMONS-535] StreamingOMSerializer drops "xml" prefixes
[WSCOMMONS-534] "prefix cannot be null or empty" with SJSXP
[WSCOMMONS-530] AXIOM DOM implementation of SOAPFaultDetailImpl only
serializes the first child node whereas the LLOM implementation
serializes all children
[WSCOMMONS-528] Unable to build axiom-api with IBM JDK
[WSCOMMONS-526] SOAPEnvelope toString() behavior inconsistant
dependent on content
[WSCOMMONS-518] Some consumers of Axiom need direct access to the
orignal parser/XMLStreamReader
[WSCOMMONS-516] Axiom Bundles are "named" the same, appear to be
running twice in ServiceMix/Karaf
[WSCOMMONS-513] Behavior of insertSiblingAfter and insertSiblingBefore
is not well defined for orphan nodes
[WSCOMMONS-505] Build Error when creating source jar fie on modules
that do not have source directory
[WSCOMMONS-502] Backward imcompatibility with Apache Abdera in Axiom
1.2.9-SNAPSHOT
[WSCOMMONS-489] StAXUtils incorrectly assumes that XMLInputFactory and
XMLOutputFactory instances are thread safe
[WSCOMMONS-488] The sequence of events produced by OMStAXWrapper with
inlineMTOM=false is inconsistent
[WSCOMMONS-487] DataHandler extension should support deferred loading/parsing
[WSCOMMONS-485] The sequence of events produced by OMStAXWrapper for
XOP:Include is inconsistent
[WSCOMMONS-483] provide help how to find a datahandler when you see
"Cannot get InputStream from
DataHandler.javax.activation.UnsupportedDataTypeException: no object
DCH for MIME type ..."
[WSCOMMONS-481] Add a method to OMFactory to create an
OMSourcedElement using a QName
[WSCOMMONS-480] Some of the serialize/serializeAndConsume methods are
declared on the wrong interface
[WSCOMMONS-479] OMDocument should have a "build" method
[WSCOMMONS-478] OMChildrenIterator based on local name has bug in
isEqual() method
[WSCOMMONS-477] Attachment order is not preserved in Axiom
[WSCOMMONS-462] axiom-api 1.2.8 is missing OSGi Import-Package to
javax.xml.stream.util under JDK 1.5
[WSCOMMONS-461] Allow StAXUtils to apply properties to XMLInputFactory
and XMLOutputFactory
[WSCOMMONS-457] Build fails on JDK 1.6
[WSCOMMONS-452] Merge org.apache.axis2.format.ElementHelper into
org.apache.axiom.om.util.ElementHelper
[WSCOMMONS-446] Serializing an MTOM SOAPEnvelope inlines the attachments
[WSCOMMONS-437] Define a common superinterface for SOAPFaultCode and
SOAPFaultSubCode
[WSCOMMONS-435]
org.apache.axiom.om.impl.dom.ParentNode.removeChild(Node) is broken
[WSCOMMONS-433] When inlining a DataHandler as Base64, OMTextImpl
doesn't stream the data
[WSCOMMONS-432] Make OMAbstractFactory work correctly in an OSGi
runtime environment
[WSCOMMONS-417] Clarify the status of the JavaMail dependency
[WSCOMMONS-414] Namespace issue in SOAP message generated
[WSCOMMONS-111] Careless exception handling needs to be fixed