[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: jboss/remoting 2.2.0.Alpha7 not compatible with jboss5

apache-tomcat is a dependency of Remoting. Remoting can't do HTTP unless those jars are present. Messaging, as a Remoting dependent, shouldn't be in the position to decide what apache-tomcat version Remoting uses. From our perspective, we don't care, and we don't want to be forced to care. All we care about is that our tests pass with the specific Remoting version listed in our dependency metadata. So, having to list apache-tomcat among our dependencies is wrong. If Remoting declares itself compatible on apache-tomcat 5.5.15, and this breaks compatibility with jbossweb 2.0.0, then jbossweb and Remoting teams need to work this out and qualify a apache-tomcat that is acceptable for both parties. Also, they need to do this in such a way that doesn't require uncomment stuff in configuration-info.xml and leave Tim and I wondering for hours why is that our testsuite fails. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020400#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...