[jboss-dev-forums] [Design of JBoss ESB] - Http Gateway - requirements please...

[tfennelly]

The HttpGateway added in v4.5 was based on an embedded tomcat, which has proven to be troublesome due to the sheer complexity of embedding tomcat.  Because of this, we have decided to go to a model similar to that of EBWS, where we generate an actual war and deploy it as a sub deployment of the containing esb deployment.

>From a usability point of view, what would people like to see in a new HttpGateway?  What I mean is ... what would they like to be able to configure, and how?  What do we want to inherit from the existing HttpGateway config?

>From an implementation point of view, what would people like to see?  Exactly the same as EBWS again, or should we try and create a new mechanism that abstracts this type of thing (creating sub deployments) away from the deployer and then use this as an opportunity to start evolving the EBWS specific code out of the deployer (where I would think it doesn't belong)?  Do we want to merge deployments of the same type as in this case, where the EBWS and the new HttpGateway both require war deployments?  What would that gain and would the added complexity be worth it?

Apart from potential implementation similarities, what else should the new HttpGateway have in common with the EBWS functionality?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237696#4237696

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237696