Mailing-List: contact beehive-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Dev" <beehive-dev@incubator.apache.org>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: beehive-commits@incubator.apache.org
To: beehive-commits@incubator.apache.org
Subject: 
 =?iso-8859-1?q?=5BApache_Beehive_Wiki=5D_Updated=3A__axis-specific_implem?=
 =?iso-8859-1?q?entation?=
Date: Thu, 09 Sep 2004 18:01:56 -0000
Message-ID: <20040909180156.85183.22064@minotaur.apache.org>

   Date: 2004-09-09T11:01:56
   Editor: JonathanColwell <jcolwell@bea.com>
   Wiki: Apache Beehive Wiki
   Page: axis-specific implementation
   URL: http://wiki.apache.org/beehive/axis-specific implementation

   no comment

Change Log:

---------------------------------------------------------------------------=
---
@@ -1,3 +1,5 @@
+=3D AXIS WSM =3D
+
 The components integrating the Jsr181ObjectModel with AXIS are as follows:
 =

 AxisHook.java - can create an org.apache.axis.description.ServiceDesc from=
 the object model's metadata.  This ServiceDesc is used within AXIS to set =
up a running service as well as to generate WSDD and WSDL documents.
@@ -7,8 +9,11 @@
 DeploymentDumper.java - a command-line tool for generating a deployment de=
scriptor based on annotations present in the web service source code.  =

 =

 =

-AXIS imports: The AXIS jars checked into beehive/wsm/lib were created from=
 a CVS checkout on September 8, 2004.  When axis 1.2 is released, the offic=
ial released libraries might be a better option.
+=3D=3D AXIS imports =3D=3D
+The AXIS jars checked into beehive/wsm/lib were created from a CVS checkou=
t on September 8, 2004.  When axis 1.2 is released, the official released l=
ibraries might be a better option.
 =

-AXIS webapp: A sample webapp is provided that should be ready to just drop=
 into your favorite servlet container.  When the beehive WSM is built, the =
webapp appears in the build/dist directory.  The included index.html will p=
oint the user to a the Foo.jws service to demonstrate the behavior of the A=
nnotatedJWSHandler.  Scripts (sorry, just .bat files now since cygwin wasn'=
t cooperating when I tried to whip up equivalent .sh scripts) to run the De=
ploymentDumper are in the AnnotationBasedDeployment directory.  These scrip=
ts will generated an annotated-server-config.wsdd which can be renamed to s=
erver-config.wsdd to add two additional web services and show the other mod=
e of annotation support.
+=3D=3D AXIS webapp =3D=3D
+A sample webapp is provided that should be ready to just drop into your fa=
vorite servlet container.  When the beehive WSM is built, the webapp appear=
s in the build/dist directory.  The included index.html will point the user=
 to a the Foo.jws service to demonstrate the behavior of the AnnotatedJWSHa=
ndler.  Scripts (sorry, just .bat files now since cygwin wasn't cooperating=
 when I tried to whip up equivalent .sh scripts) to run the DeploymentDumpe=
r are in the AnnotationBasedDeployment directory.  These scripts will gener=
ated an annotated-server-config.wsdd which can be renamed to server-config.=
wsdd to add two additional web services and show the other mode of annotati=
on support.
 =

-Oustanding Issues:  The two methods of integration with AXIS outlined abov=
e are most definitely works in progress.  Anyone with a solid understanding=
 of the inner workings of AXIS is cordially invited to comment on, criticiz=
e, fix or rearchitect these first drafts.  At the moment, the parts of the =
web service successfully customized using the JWS approach such as portType=
 and serviceName are not working in the DeploymentDumper/WSDD approach whil=
e the opposite is true for the binding name.
+=3D=3D Oustanding Issues =3D=3D
+The two methods of integration with AXIS outlined above are most definitel=
y works in progress.  Anyone with a solid understanding of the inner workin=
gs of AXIS is cordially invited to comment on, criticize, fix or rearchitec=
t these first drafts.  At the moment, the parts of the web service successf=
ully customized using the JWS approach such as portType and serviceName are=
 not working in the DeploymentDumper/WSDD approach while the opposite is tr=
ue for the binding name.