[wsas-java-dev] Axis1 Deployer for Axis2

[Glen Daniels]

Yes, dims, but nobody responded yet. :)  I'm not sure I understood your 
question - were you asking if we'd end up with a single Axis2->1 bridge 
jar that people could plug in to existing A2 installations?

As for the rest of the thread so far:

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.

As others have said, a Synapse/ESB solution can get you Axis1 
front-ending but at the cost of extra network roundtrips.  There may be 
good reasons to do that, but having an intra-JVM solution is still nice 
from a performance and management standpoint.

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.

--Glen

Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Did my email below reach this list??
> 
> thanks,
> dims
> 
> Davanum Srinivas wrote:
>> Just to clarify the decision, all the code directly in wsas svn totally integrated right? (So there is no single jar
>> that anyone can use with an existing Axis2 installation)
>>
>> thanks,
>> dims
>>
>> Sanjiva Weerawarana wrote:
>>> I'd like to put it into WSAS .. and even have a bit of UI to help users
>>> deploy an Axis1 service easily. Azeez, what do you think? This'll be a
>>> very good feature for users .. good enticement for WSAS.
>>> A good usecase: deploy Axis1 service and use Axis2's security + RM in
>>> front of it. This is a bit ESB-like because the scenario can be dealt
>>> with ESB+Axis1 too but IMO that's ok as its a single JVM solution. ESB
>>> folks what do you think?
>>> Glen, can we try to get the fault stuff sorted before we ship WSAS 2.0?
>>> Sanjiva.
>>> Glen Daniels wrote:
>>>> Hi folks!
>>>>
>>>> As part of my work the last month or two, I've built a custom deployer
>>>> which allows you to use Axis1 "inside" of Axis2.  You install the
>>>> deployer and then it notices WSDD files inside your Axis2 respository
>>>> - it spins up an Axis1 AxisEngine configured with the WSDD, and then
>>>> steps through each service in that engine, and deploys for it a
>>>> "proxy" Axis2 service with a custom MessageReceiver that dispatches to
>>>> Axis1.
>>>>
>>>> The theory here is that this should allow current Axis1 users to
>>>> continue using their (potentially RPC-style) services for a while, but
>>>> still get the benefits of the Axis2 flow/Module architecture.
>>>>
>>>> The current version is a first cut - it doesn't handle faults well
>>>> yet, for example, and it needs some improving.  But I'd like to get it
>>>> plugged into the source repository so people can play with it.
>>>>
>>>> So here's my question for you.  Where should I check this in?  In WSO2
>>>> commons?  WSAS?  Suggestions and/or comments appreciated.
>>>>
>>>> Thanks,
>>>> --Glen
>>>>
>>>> _______________________________________________
>>>> Wsas-java-dev mailing list
>>>> Wsas-java-dev at wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>>>>
>>
> 
> _______________________________________________
> Wsas-java-dev mailing list
> Wsas-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
> 
> 
> 
> - --
> Davanum Srinivas (dims at wso2.com)
> Co-Founder & Director, Customer Engagements, WSO2 (http://wso2.com)
> Yahoo IM: dims Cell/Mobile: +1 (508) 415 7509
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
> 
> iD8DBQFGXVeXgNg6eWEDv1kRAtBhAJ4+jvLeikkHeKj8HvEXfcmAjytpgACgkoPv
> 08WKGqMVLJhN6sVDRTQsC5U=
> =xPme
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Wsas-java-dev mailing list
> Wsas-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev