Thanks for this first start point. I'll have a look at the sources... I confess i'd hoped a little bit more... Thanks anyway.
>>> -----Original Message----- >>> From: Mike Barton [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, June 21, 2005 4:56 PM >>> To: [email protected] >>> Subject: Re: AXIS 1.2 / OSCAR - How to automate server services >>> deployment >>> >>> >>> I would recommend that you start looking at AxisEngine and >>> WSDDGlobalConfiguration to better understand how Axis manages >>> deployments. >>> >>> As for partitioning, it all depends on your requirements. From an ease >>> of management perspective, I would suggest using a single instance of >>> Axis, managing multiple services. But, again it all depends on your >>> requirements. >>> >>> Ephemeris Lappis wrote: >>> > Hello. >>> > >>> > 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 >>> > >>> > >>> > >>>
