axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ephemeris Lappis" <>
Subject AXIS 1.2 / OSCAR - How to automate server services deployment
Date Tue, 21 Jun 2005 11:34:22 GMT

I'm working on a test to evaluate the difficulty level of an automated
service deployment in an axis server embeded in an OSGi bundle...

I've quickly made a first prototype of server side deployment descriptor
generation, starting with a wsdl input and a given implementation class.
This first test uses the org.apache.axis.wsdl.toJava.Emitter to generate the
deploy.wsdd, and then merges it with the axis server-config.wsdd. Then, an
AxisServlet instance is bound to the OSGi HttpService. This solution works
for a single service and a unique deployment.

Now, i realistic bundle should take into account multiple services that may
dynamically be deployed and undeployed...

What is the better start point in the axis server classes to handle these
hot deployment and undeployment ? To preserve the total partition between
services, is it better to create a new servlet for each service port ? Or,
is there a better way to use a single servlet and add or remove services ?

Thanks for your help.

Ephemeris Lappis

View raw message