[esb-java-dev] tomcat/war support

[Paul Fremantle]

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.

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

Office: +1 646 290 8050
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com