Actually, there is no HTTPLocator. I meant the Locator class on Remoting.
And for HTTPInvoker I meant HTTPTransporter
I made a modification to make the invoker classes load lazily (meaning won't encounter this problem unless actually using the http invoker, which is based on tomcat connectors). However, is still an issue when using http transport.
This is also a problem regardless of setting UseJBossWebLoader attribute in jbossweb-tomcat55.sar/META-INF/jboss-service.xml. Only current solution is to copy following jars to the server lib directory:
As Clebert said, these are already present within the jbossweb-tomcat55.sar, but are not accessible to remoting.
Note, this is only currently an issue when using jboss-remoting.jar build from JBossRemoting HEAD. However, this is basically the same code that is going to be in the JBossRemoting 1.4.0 release, which I would like to include in the JBossAS 4.0.4 release.
Create a JBAS jira integration issue for this remoting/tomcat sar jar issue as this should not exist. The tomcat sar is not scoped.