6 Replies Latest reply on Oct 22, 2002 8:09 AM by Peter Doornbosch

    Exact JARs for a Client

    Fabricio Newbie

      Hi. I want to know which are the Jars necessary for a typical (remote) client. I account for:

      *jboss-common-client.jar
      *jboss-client.jar
      *log4j.jar
      *jnp-client.jar
      *jaas.jar
      *jbosssx-client.jar

      Question: am i missing any jar? Could i NOT include any of these mentioned jars?

      Thanks in advance!!!

        • 1. Re: Exact JARs for a Client
          Noel Hebert Newbie

          Fabricio,

          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.

          Cheers,

          Noel.


          • 2. Re: Exact JARs for a Client
            Fabricio Newbie

            Thanks a lot. Your opinion is worth taking into account. However, do you know where can that info be found? Cheers from Bs. As..

            • 3. Re: Exact JARs for a Client
              Eric Cire Newbie

              Me too.

              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:

              jboss-common-client.jar
              jboss-client.jar
              jbosssx-client.jar
              jboss-j2ee.jar
              log4j.jar
              jnp-client.jar
              jaas.jar

              • 4. Re: Exact JARs for a Client
                Greg Turner Apprentice

                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.

                • 5. Re: Exact JARs for a Client
                  Peter Doornbosch Apprentice

                  > 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...

                  Cheers,
                  Peter

                  • 6. Re: Exact JARs for a Client
                    Peter Doornbosch Apprentice

                    (retry of posting attachment)