Date: 2004-09-09T10:59:34 Editor: JonathanColwell <[EMAIL PROTECTED]> Wiki: Apache Beehive Wiki Page: axis-specific implementation URL: http://wiki.apache.org/beehive/axis-specific implementation
no comment New Page: 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. AnnotatedJWSHandler.java - a subclass of org.apache.handlers.JWSHandler that uses reflection to examine the annotations in a compiled JWS Class. These annotations are then used to configure some portions of the web service. DeploymentDumper.java - a command-line tool for generating a deployment descriptor 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 official released libraries 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 point the user to a the Foo.jws service to demonstrate the behavior of the AnnotatedJWSHandler. Scripts (sorry, just .bat files now since cygwin wasn't cooperating when I tried to whip up equivalent .sh scripts) to run the DeploymentDumper are in the AnnotationBasedDeployment directory. These scripts will generated 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 annotation support. Oustanding Issues: The two methods of integration with AXIS outlined above are most definitely works in progress. Anyone with a solid understanding of the inner workings of AXIS is cordially invited to comment on, criticize, 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 while the opposite is true for the binding name.
