[esb-java-dev] tomcat/war support

[Sanjiva Weerawarana]

Asankha C. Perera wrote:
> 
> The difference between Axis2 and Synapse is that with a blocking servlet 
> model, an ESB can easily exhaust all threads. This can be even shown for 

I know all that :) .. but what I'm saying is that it should be possible 
for someone to use Synapse/ESB as a regular old Axis2 module without 
anything extra! The limitations you mention are part of Axis2 (and any 
other WS-* runtime that uses regular servlets) too - and its something 
users are willing to live with obviously (for some scenarios at least).

>> I agree we need to keep the NIO model in its native form, of course. 
>> However, I'm not convinced that people won't be really surprised that 
>> they deploy as a war but need to go to a port different from the 
>> servlet container's port to access the features!
> No.. the luckily ESB console runs off the default port of the container :-)

Yeah but that's irrelevant - how does the user find out what port to use 
for example?

>> Can you guys ask the user who asked for this and get his/her opinion?
> http://mail-archives.apache.org/mod_mbox/ws-synapse-user/200707.mbox/%3cB319B58E71D8C6469773C11686024E69F7841B@exbah01.e-Space.local%3e 

OK so this user seems to not have a problem with it.

I still don't understand why you're opposed to just making it work right 
as a "regular" Axis2 module and simply document all the limitations it 
comes with!

Oh BTW have you guys made progress with moving the NIO transport to Axis2? 
Axis2 needs that too for sure.

Sanjiva.
-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: sanjiva at wso2.com; cell: +94 77 787 6880; fax: +1 509 691 2000

"Oxygenating the Web Service Platform."