I've started work on this JIRA on trunk and I wanted to briefly explain what I'm planning to do a and I'd like to get an answer to a couple of questions I had:
As suggested by Scott in a jboss-dev email thread, I'm creating a test config so that we can eventually distribute http invokers based on JBoss Remoting. This config will contain something along these lines (uinvoker -> unified invoker):
On top of that, for the new http invoker to deploy, I need deploy/http-invoker.sar/invoker.war/WEB-INF/classes folder to be available to http-uinvoker.sar. In fact, I need org.jboss.invocation.http.servlet.NamingFactoryServlet available so that http unified version of JNDI factory can be deployed. For the time being, I'm gonna be copying the classes folder from deploy/http-invoker.sar/invoker.war/WEB-INF/ right after test configuration has been created. Alternatively, this and other relevant http invoker relevant classes could go in a jar in lib/ directory. What's people's preference?
With regards to the tests to be run with this new invoker, looking around the testsuite, I've found the following tests that use http invoker for ejb invocations or jndi lookups:
Currently, my preference is to create a separate bunch of tests that are run under this new test configuration that uses the unified http invoker and leave the current tests running with current http invoker. These new tests would also ideally EJB3 tests using http unified invoker but we can leave those for later, when we've swapped the default http invoker distribution as these tests would live in the separate EJB3 project. Now, if I was to create these new tests that used beans configured with new http unified invoker, where shall I store them? Do people have other preferences?