"tfennelly" wrote : I agree that merging them is ideally what we want, but given the current arch where the listeners are tied in with the services etc, merging what are essentially 2 separate listeners together (as alike and all as they are) without them both being based on a common "framework" would only seem possible (to me) via a hack. But this is not done at the listener level, it is done during deployment. It would be straight forward to handle this in a clean manner, without any need for hacks. "tfennelly" wrote : I'm not really suggesting a "fully extensible" framework... more like a "common" framework/codebase that the Http Gateway and EBWS would build off. Sure, we are in agreement here. The first version wasn't that though, which is what I was referring to. "tfennelly" wrote : It's not the end result that's complex in my view, so you are right... there's nothing complex about adding more servlets into a deployment. For me, it's about how you achieve this in the current deployer i.e. gather together the info to create the single war, without it being a hack.[/quote | There is no need for this to be a hack. | | "tfennelly" wrote : In the current arch where we don't have a common codebase for doing this and EBWS cannot be built upon (in its current form), shoehorning http in alongside it would end up being a hack. Hence I think we need to rework some of EBWS in order to get a common base upon which this stuff can be built. | Definitely, the outcome of this has to be a cleaning up of what we currently have. How can they be merged otherwise? | | Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238199#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...