Return-Path:
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 27150 invoked from network); 19 Apr 2006 05:52:10 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 19 Apr 2006 05:52:10 -0000
Received: (qmail 69719 invoked by uid 500); 19 Apr 2006 05:52:09 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 69657 invoked by uid 500); 19 Apr 2006 05:52:09 -0000
Mailing-List: contact axis-cvs-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
List-Post:
List-Id:
Delivered-To: mailing list axis-cvs@ws.apache.org
Received: (qmail 69646 invoked by uid 500); 19 Apr 2006 05:52:09 -0000
Delivered-To: apmail-ws-axis2-cvs@ws.apache.org
Received: (qmail 69643 invoked by uid 99); 19 Apr 2006 05:52:09 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2006 22:52:09 -0700
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194)
by apache.org (qpsmtpd/0.29) with SMTP; Tue, 18 Apr 2006 22:52:08 -0700
Received: (qmail 27010 invoked by uid 65534); 19 Apr 2006 05:51:48 -0000
Message-ID: <20060419055148.27009.qmail@minotaur.apache.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r395145 -
/webservices/axis2/trunk/java/xdocs/latest/OMTutorial.html
Date: Wed, 19 Apr 2006 05:51:48 -0000
To: axis2-cvs@ws.apache.org
From: chinthaka@apache.org
X-Mailer: svnmailer-1.0.8
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
Author: chinthaka
Date: Tue Apr 18 22:51:45 2006
New Revision: 395145
URL: http://svn.apache.org/viewcvs?rev=395145&view=rev
Log:
Some more changes to OMTutorial. Committing in chunks.
Modified:
webservices/axis2/trunk/java/xdocs/latest/OMTutorial.html
Modified: webservices/axis2/trunk/java/xdocs/latest/OMTutorial.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/xdocs/latest/OMTutorial.html?rev=395145&r1=395144&r2=395145&view=diff
==============================================================================
--- webservices/axis2/trunk/java/xdocs/latest/OMTutorial.html (original)
+++ webservices/axis2/trunk/java/xdocs/latest/OMTutorial.html Tue Apr 18 22:51:45 2006
@@ -132,7 +132,7 @@
Since OM is a differed built object model, It incorporates the concept of
caching. Caching refers to the creation of the objects while parsing the pull
stream. The reason why this is so important is because caching can be turned
-off in certain situations. if so the parser proceeds without building the
+off in certain situations. If so the parser proceeds without building the
object structure. User can extract the raw pull stream from OM and use that
instead of the OM. In this case it is sometimes beneficial to switch off
caching. The advanced operations section explains more on accessing the raw
@@ -161,16 +161,9 @@
-The easiest way to obtain the OM binary is to download the Axis2 minimal
-binary distribution. The lib
-directory will contain the axis2-core-1.0.jar.
+The easiest way to obtain the OM binary is to download the latest release from here
However more adventurous users can build the OM from source, which is
-described in the next section. In this way one get only the "OM
-jar".
+described in the next section.
Detailed information on getting source from Axis2 SVN repository can be
found here.
@@ -179,16 +172,15 @@
Linux move it to the project directory and execute the command "maven jar".
All other necessary jars will be automatically downloaded. When the build finishes
-successfully, the axis2-xml-1.0.jar can
-be found in the newly created "targets" directory in the XML
-module.
+successfully, the axiom-api-.jar and axiom-impl-.jar can
+be found in the newly created "targets" directory.
Once the OM-binary is obtained by any of the above ways , it should be
included in the classpath for any of the OM based programs to work.
Subsequent sections of this tutorial assume that this build step is complete
-and the axis2-core-1.0.jar
-or axis2-xml-1.0.jar is
-correct in the classpath along with the StAX API jar file and a StAX
+and axiom-api-.jar
+ and axiom-impl-.jar are
+present in the classpath along with the StAX API jar file and a StAX
implementation.
Creation