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

[Kevin.Conner@jboss.com]

"tfennelly" wrote : 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)?

EBWS and the http gateway are essentially the same animal and should be shared.  There are very few differences between the two, especially once we extend EBWS to support what will be available to HTTP.

We should definitely take this code out of the deployer but going to the extent of a fully extensible framework is not required.  We only need to support HTTP and EBWS.

"tfennelly" wrote : 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?
Yes, these should be merged into the same war file so that we have a single deployment.  Even with the current EBWS code we already have an issue where we conflict with other deployments,  Expanding the number of these deployments, especially when not necessary, seems strange to me.

BTW what added complexity do you get from adding more servlets into a deployment?  Can you expand on where you think the issue lies?

"tfennelly" wrote : Apart from potential implementation similarities, what else should the new HttpGateway have in common with the EBWS functionality?
I'll try and cover this later when I post about the original plans.

Kev

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

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