[wsas-java-dev] Re: [esb-java-dev] Joint Use case of WSAS and ESB

[Asankha C. Perera]

Hi Dims
> That would be perfect! but is it do-able in the short-term? or long-term? 
This is do-able in the short term. Right now how we start Synapse / ESB 
is by starting a custom Axis2 server, thats configured to load 
Synapse/ESB as a module. So basically this same thing will work even on 
a clean Axis2 / WSAS. We must however test this with the non-NIO 
transport, and thus it is tied with the other question on WAR 
deployment. Thus I will get Upul to try this out tomorrow and give an 
update ASAP
> I'd like for our customers to use the
> additional stuff in our ESB also in addition to what's in synapse. Please take that into account as well.
>   
The ESB is Synapse + the enhanced registry and the admin console. Maybe 
an option here is to separate the ESB Runtime from the admin console - 
lets see how feasible or appropriate this would be too. Something cool 
this would allow us to do is to be able to direct the console at a 
pre-defined ESB instance and monitor and manage it. Then it would also 
be possible to add more instances, say in a cluster or in different 
organizational units to the console and manage everything from a central 
place.

thanks
asankha
> thanks,
> - -- dims
>
> Asankha C. Perera wrote:
>   
>> Dims
>>
>> Since you are talking about a the ESB as a module that simply runs over
>> an existing Axis2/WSAS instead of starting an Axis2 instance underneath,
>> we need to first address http://issues.apache.org/jira/browse/SYNAPSE-121
>>
>> I believe this should be a .mar distribution of the ESB (or Synapse) for
>> this scenario, driven off a mostly static synapse.xml
>>
>> thanks
>> asankha
>>
>> Davanum Srinivas wrote:
>> Team,
>>
>> Am looking for a good joint use case of both WSAS and ESB together (in
>> a production environment, needless to say! :) So
>> far the best i came up with was the following:
>>
>> Deploy Axis1 legacy service AND a newer Axis2 Service on WSAS and drop
>> in ESB jars to implement versioning/routing based
>> on some on-the-wire information (say SOAP12 goes to Axis2?). Am trying
>> to think how we could encourage our customers to
>> upgrade from Axis1 to WSAS and a good versioning story seems to be
>> something that will help folks decide to upgrade
>>
>> Thoughts? Ideas? Comments? Any better scenarios?
>>
>> In addition to settling down on one or a few scenarios, Can we please
>> make sure that the next versions of WSAS and ESB
>> can co-exist say in the same servlet container (same war) and w/o
>> opening additional sockets.
>>
>> thanks,
>> dims
>>
>>     
> _______________________________________________
> Esb-java-dev mailing list
> Esb-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/esb-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)
> 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)
>
> iD8DBQFG1AsXgNg6eWEDv1kRAl0uAJ4w5NFPFDfzooGTEOXeq5ys4tM7dQCdFp78
> 41mYotSrxJ+2UbdcbI66B1M=
> =c+VF
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Wsas-java-dev mailing list
> Wsas-java-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://wso2.org/pipermail/wsas-java-dev/attachments/20070828/28f55542/attachment.htm