5 Replies Latest reply on Oct 9, 2009 6:29 AM by Tim Fox

    jbossall-client.jar and the jar hell at remote JBM client

    bodrin b. Newbie

      [JBM.1.4.0.SP3 \ jboss-4.2.2.GA]


      From a remote JBM client point of view we need some JBoss jars including jbossall-client.jar (http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP3/html/installation.html#inst.remoteclient). I see two main problems with this:

      1) The order of this jars does matter - this I think is not even mentioned into the docs, but if you list them into your classpath into a different order it will not work some times. The bigger problem is that in some places/containers there is no way to specify any such order like in tomcat for example.

      2) If your project uses some library which is duplicated in jbossall-client.jar also and the versions are different - again we have a problem. One such example is hibernate.

      I have found in this thread http://www.jboss.org/index.html?module=bb&op=viewtopic&t=153853&postdays=0&postorder=asc&start=10 that

      jbossall-client.jar is an evil aggregation of jars. You will need to use the individual client jars from /jboss/client. I have changes the examples to make use of the correct jars, and we have documented the minimal set for JBM, but depending on the other EE features you use you may need to add more client jars...

      So, the question is what is the minimal set of client jars needed for a remote JBM client?
      And does this will solve problem 1) ?