3 Replies Latest reply on Jan 5, 2006 11:59 AM by Scott Stark

    Dependency on coyote.jar

    Clebert Suconic Master

      I have tested JBossRemoting/head integrated with Head, and I realized something.

      Due to the recent changes on HTTPInvoker, HTTPLocator is loading transporters for HTTP which is depending on coyote.jar (and some other tomcat libraries).

      It happens that WEBClassLoader being used by UnifiedInvokers doesn't have access to the classLoader that is loading coyote.jar. So, a temporary fix would be to copy these libraries under /lib.

      Is there a way we could have these classes on the classpath without having to copying then to /lib? (Any classLoader operation we could use?)


        • 1. Re: Dependency on coyote.jar
          Clebert Suconic Master

          Actually, there is no HTTPLocator. I meant the Locator class on Remoting.

          And for HTTPInvoker I meant HTTPTransporter

          • 2. Re: Dependency on coyote.jar
            Tom Elrod Master

            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.

            • 3. Re: Dependency on coyote.jar
              Scott Stark Master

              Create a JBAS jira integration issue for this remoting/tomcat sar jar issue as this should not exist. The tomcat sar is not scoped.