Take the soft option and include the lot
in ./client in whatever directory JBoss is
installed. I am assuming JBoss 3.0...
It may prove to be a false economy to try to
eliminate un-necessary jar files when you may
or may not know what the potiential clients are
supposed to accomplish.
Just some random thoughts.
Thanks a lot. Your opinion is worth taking into account. However, do you know where can that info be found? Cheers from Bs. As..
I'd like to know the exact list. The entire clients directory is pretty big, I'd rather not include all of it in a download if possible.
I've gotten away with just these:
Here is an algorithm to get you the info you want.
Write yourself an quick and dirty app with main where you tell the app a directory and fully qualified class name. Program the app to search in the directory and all sub directories for all jars (wars, sars, ears, etc) and look for your class in the jar.
Now, turning to your main application, only put in your class path those jars that allow your app to be compiled. Do this by trial an error, removing jars from class path and seeing if your app compiles.
Then run your main app and when you get a class not found error, use the quick and dirty program above to look for which jar the class is in and add that jar to class path. Repeat as needed until your app runs without errors.
> Write yourself an quick and dirty app with main where
> you tell the app a directory and fully qualified
> class name. Program the app to search in the
> directory and all sub directories for all jars (wars,
> sars, ears, etc) and look for your class in the jar.
Or use the attached shell script, which performs the same task...
(retry of posting attachment)