[esb-java-dev] tomcat/war support

[Davanum Srinivas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I understand. Then we need to take care of additional stuff.

for example, How good are we in terms of a clean shutdown of the additional transports? Say if someone uses the weblogic
UI to shutdown the container, do we exit cleanly?

Also, Would it be better to start the transport outside the servlet since containers forbid starting threads? I know
weblogic and websphere have hooks for that.

thanks,
dims

Paul Fremantle wrote:
> Sanjiva
> 
> I agree - with a caveat. I think we need support for BOTH. There are two
> different use cases:
> 
> 1) We had at least one user whose organization ONLY allowed the Tomcat
> servlet ports to be opened on the firewall - so the only way of getting
> work into the system is via servlets. So for that user we *must* allow
> the servlet transport to work.
> 
> 2) There are other users whose corporate policies are based on hosting
> within an AppServer (e.g. Tomcat, BEA, JBoss, WebSphere etc) For these
> users, the servlet transport isn't the issue, but having the ESB running
> in the managed appserver environment is. They may still want and need
> the non-blocking IO model.
> 
> Paul
> 
> Sanjiva Weerawarana wrote:
>> As far as I understand it, the current claimed support for WAR
>> deployment has the ESB opening another port .. and the WAR is simply
>> used to start the ESB.
>>
>> Is that correct?
>>
>> If so that's totally not what is needed IMO. (Not to mention the fact
>> that that breaks the J2EE programming rules!)
>>
>> We need to make sure that WAR deployment means the requests come via
>> the servlet container and the ESB mediates the requests and forwards
>> them on or whatever. Yes I know the service limitations it implies but
>> don't forget most Web service runtimes are operated that way.
>>
>> So, what does it take to fix it to work right?
>>
>> Sanjiva.
> 


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

iD8DBQFG1AwVgNg6eWEDv1kRAlOdAKDY/jbO29aeV22P4NvzhWmkJP2VNACgxd2j
Lm610Yxb5FjAYIKwIxPs1Fo=
=X6my
-----END PGP SIGNATURE-----