[wsas-java-dev] Axis1 Deployer for Axis2

[Chathura C. Ekanayake]

Ruwan Linton wrote:
> 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?
>
> From the Synapse/ESB side Axis1 service is just an endpoint, so we 
> already support this feature (ESB+Axis1 endpoint with RM and Sec 
> engaged).
>
> At the same time, we can let the users deploy Axis1 services in to 
> Synapse/ESB as a proxy service (in Synapse) by using this custom 
> deployer. (Should be post 1.0)
>
>
> Ruwan.

Synapse/ESB can be used to provide security + RM to any web services 
engine that inter-operate with Axis2. As Ruwan mentioned, any such 
engine (including Axis1) can be represented by a Synapse endpoint. So, 
if we want to use Axis1 service with Security, RM, etc, we can put ESB 
in front of Axis1 and let the client talk with the ESB using security 
and RM. Then ESB can forward those messages to the Axis1 without any 
such features. Here we assume that ESB and Axis1 are running in a secure 
and reliable network. Custom Axis1 deployer is not necessary to support 
this scenario for Synapse/ESB.

But if we want to support Axis1 services with WSAS as a single JVM 
solution, this custom deployer would be a nice thing to have.

Chathura
>>
>>
>> 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
>