What remote client libs are required ??

[patrick1]

Hi,

I am trying to migrate our ejb3 application from JBoss 4.2.3 to JBoss 5.1.0. The application is accessed by a swing rich client and deployed using Java Web Start.

With JBoss 4.2.3 I used to include on the client side the jbossall-client.jar lib. Now with 5.1, The $JBOSS_HOME/client/jbossall-client.jar library that used to bundle the majority of jboss client libraries, is now referencing them instead through the Class-Path manifest entry. This requires that you have jbossall-client.jar together with the other client/*.jar libraries, so they can be found.

Is this the only solution ? I mean I can't realisticaly bundle tens of jars in my JavaWebStart app while before I only had to bundle one ! Plus I don't think I need to include the 98 jar that can be found in $JBOSS_HOME/client

Has anyone any pointers ?

Thanks,
- Patrick

[f_marchioni]

Having the client libs declared in the MANIFEST file avoid the burden of setting manually the classpath at client level, however you have to provide the client jars needed.

You might bundle all client libs into a single library, or you can as well find out the libraries which are actually required by your application and modify the manifest-file accordingly.

hope it helps...
Francesco

[peterj]

You can use JBoss Tatttletale to find out the actual set of JARs you need. (Look at the tabs at the top of this web page - Tattletale is under Projects > Tools)