[wsas-java-dev] Axis1 Deployer for Axis2

[Glen Daniels]

Hi Sanjiva:

Sanjiva Weerawarana wrote:
> Glen Daniels wrote:
>> Putting it into WSAS would be OK.  The thing about deploying Axis1 
>> services is that it's often not as simple a packaging model as Axis2 - 
>> in particular, there's no archive management or classpath isolation, 
>> so in A1, you need to set up the service classes yourself and make 
>> sure they're somehow on the classpath.
> 
> Can't we make that work nicely? That is, it seems to me we should be 
> able to allow a user to jar up all the classes of the Axis2 service, 

s/Axis2/Axis1/?

> upload any dependent jars and then bundle all that into a classpath that 
> is visible to the A1 deployer and let it go. That way we can get near 
> the convenience of Axis2.

Yup.  As long as the classpath is set up nicely for the A1 deployer, 
that means it's also set up for the (A1) AxisEngine.

>> When's the projected WSAS 2.0 date?  It shouldn't take that long to 
>> clean up the fault stuff, maybe a few days work pulling together tests 
>> and building bridges.
> 
> Let's get the code + the easy deployment UI integrated to WSAS 2.0!

See other thread - I think the deployer itself feels more appropriate in 
commons, so that people can use it w/o WSAS.  Then WSAS makes it better 
with deployment/tooling help, etc.  Haven't heard anything else 
recently; if people are OK with that, I'll check it in and we can start 
working on UI!

--Glen