Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 7355 invoked from network); 6 Jun 2005 12:30:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jun 2005 12:30:27 -0000 Received: (qmail 17749 invoked by uid 500); 6 Jun 2005 12:30:23 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 17670 invoked by uid 500); 6 Jun 2005 12:30:23 -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 17635 invoked by uid 99); 6 Jun 2005 12:30:23 -0000 X-ASF-Spam-Status: No, hits=-9.8 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 06 Jun 2005 05:30:17 -0700 Received: (qmail 7039 invoked by uid 65534); 6 Jun 2005 12:30:05 -0000 Message-ID: <20050606123005.7038.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: svn commit: r180305 - in /webservices/axis/trunk/java: modules/samples/maven.xml xdocs/Axis2ArchitectureGuide.html xdocs/faq.html Date: Mon, 06 Jun 2005 12:30:04 -0000 To: axis-cvs@ws.apache.org From: hemapani@apache.org X-Mailer: svnmailer-1.0.0-dev X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: hemapani Date: Mon Jun 6 05:30:03 2005 New Revision: 180305 URL: http://svn.apache.org/viewcvs?rev=3D180305&view=3Drev Log: improve the archi guide Added: webservices/axis/trunk/java/xdocs/faq.html Modified: webservices/axis/trunk/java/modules/samples/maven.xml webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html Modified: webservices/axis/trunk/java/modules/samples/maven.xml URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/modules/samp= les/maven.xml?rev=3D180305&r1=3D180304&r2=3D180305&view=3Ddiff =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- webservices/axis/trunk/java/modules/samples/maven.xml (original) +++ webservices/axis/trunk/java/modules/samples/maven.xml Mon Jun 6 05:30:= 03 2005 @@ -17,7 +17,7 @@ tofile=3D"target/test-resources/repository-client/modules/addressing.mar= "/> + tofile=3D"target/toWar/services/version.aar"/> =20 Modified: webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/Axis2A= rchitectureGuide.html?rev=3D180305&r1=3D180304&r2=3D180305&view=3Ddiff =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html (original) +++ webservices/axis/trunk/java/xdocs/Axis2ArchitectureGuide.html Mon Jun = 6 05:30:03 2005 @@ -273,8 +273,8 @@

Module Archive

=20

Module archive must have a META-INF/module.xml file and depend= ent classes the module.xml file has Module parameters and the Oper= ations defined in the module.

=20 -

When the system started up the Axis2 ask the deployment model to creat= e a Axis Configuration, the Deployment Model first find a server.xml or a c= lient.xml file and build the global configuration. Then the Model check for= the Module archives and then for the service archives, the corresponding = services and Modules are added to the Axis Configuration. System will buil= t a Contexts on top of the Axis Configurations and the Axis2 is ready to se= nd or receive the SOAP Message. The Hot deployment is allowed only for the = Service and in that case a thread will check the repository repeatedly, and= add the Service corresponds to the new found Service archives to the repos= itory. =20 -

+

When the system started up the Axis2 ask the deployment model to creat= e a Axis Configuration, the Deployment Model first find a server.xml or a client.xml file and build the global configuration. Then t= he Deployment check for the Module archives and then for the service archiv= es, the corresponding services and Modules are added to the Axis Configurat= ion. System will built a Contexts on top of the Axis Configurations and the= Axis2 is ready to send or receive the SOAP Message. The Hot deployment is = allowed only for the Service and in that case a thread will check the repos= itory repeatedly, and add the Service corresponds to the new found Service = archives to the repository. +

=20 =20

WSDL and code generation

@@ -313,10 +313,10 @@ Client API, the implementation is based on a class called MEPClient= and there are extentions for each Message Exchange Pattern that Axi= s2 Client API supports.

=20

One Way Messaging Support

-

The One-Way support is provided by the InOnlyMEPClient an= d Axis2 provides a class called Call that provides a much simpler interface= for the user. The Axis2 supports HTTP/SMTP and TCP transports, in the case= of the HTTP transport the return channel is not used and the HTTP 202 OK i= s returned in the - return Channel.

+

The One-Way support is provided by the InOnlyMEPClient an= d Axis2 provides a class called Call that provides a much simp= ler interface for the user. The Axis2 supports HTTP/SMTP and TCP transports= , in the case of the HTTP transport the return channel is not used and the = HTTP 202 OK is returned in the return Channel. +

Request Response Messaging Support

=09 -

The Request-Response support is provided by the InOutMEPCl= ient and Axis2 provides a class called MessageSender that provides a= much simpler interface for the user. The Client API has four ways to confi= gure a given Message Exchange

+

The Request-Response support is provided by the InOutMEPCl= ient and Axis2 provides a class called MessageSender th= at provides a much simpler interface for the user. The Client API has four = ways to configure a given Message Exchange

  1. Blocking or Non-Blocking nature - this can be decided by usi= ng invokeBlocking() or invokeNonBlocking() method= s
  2. Sender transport - transport use to send the SOAP Message Added: webservices/axis/trunk/java/xdocs/faq.html URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/faq.ht= ml?rev=3D180305&view=3Dauto =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D (empty)