Smallest JMS Client footprint?

Question

          Hi everyone,
          I would like to deploy a JMS client applet and avoid downloading the 38MB weblogic.jar
          file. The WebLogicThinClient whitepaper gives a few suggestions on how to reduce
          the size of the JAR file. After getting the first method to work (using utils.verboseTozip),
          I'm left with a JAR file containing 1058 class files and weighing in at a little
          over 5 Mb. Is this really the smallest set of files required to support JMS functionality?
          Thanks,
          Elias
          

Answer 1

Hi Elias,
          I don't know the answer the to all your problems, hopefully someone else
          in the newsgroup can contribute here. More in-line.
          Tom
          [email protected] wrote:
          > Hi again,
          >
          > I've been experimenting with the URLClassLoader and you were right, the
          > JAR file produced using this method is much smaller (1Mb) than the one
          > produced with the verboseToZip utility (5Mb). Furthermore, I am now able
          > to run my JMS tests without seeing any exceptions.
          As a safety precaution: if you plan on disabling the URLClassLoader once
          you've got the classes, you may wish to consider including all "Exception"
          classes that occur in the same package as any other class you download.
          This is in case your tests don't cover all error conditions...
          > Unfortunately, there
          > are still a couple of vexing problems:
          >
          > Just after starting the URLClassLoader program the following message
          > appears.
          > "Unable to access Localizer, weblogic.i18n.L10nLogLocalizer"
          > Not one of the jar files in the server/lib directory contains this
          > class. There is a L10nLogLocalizer.properties file, which should be
          > located by the URLClassLoader but isn't...?
          I think you're correct. I'm not sure how to force the URLClassLoader
          to find such files. If you find out, please let me know.
          In this case, I think this file is only used for localizing client side log messages that
          get dumped to stdout, but there are very few such messages. If your app runs,
          I think you can safely ignore the "Unable to access..." message.
          >
          >
          > After setting up the JMS environment (connections, sessions, producers,
          > consumers, etc.), the test driver publishes some messages of different
          > types. The onMessage() method I implemented should print out "received X
          > message", where X is the message type. Unfortunately, I don't see this
          > message printed out at all and instead see "testSync TX = null" instead.
          > I have no idea what this means, but it appears that the onMessage()
          > method is not being invoked for some reason. Do you have any idea what
          > this indicates?
          No.
          > Am I somehow missing a class that I need?
          To narrow down the problem:
          Try with the full weblogic.jar in the applet.
          Try running as regular client with full weblogic.jar, then with your small.jar.
          > Has anyone
          > else ever seen this message print out when they were expecting something
          > else? Thanks again for any assistance, I feel quite close to a workable
          > solution! Please let the BEA developers working with JMS that the "thin
          > JMS client" JAR file will be well received.
          Just send cash directly to BEA's Liberty Corner, NJ site.
          >
          >
          > Elias
          >
          > Tom Barnes wrote:
          >
          > > The URLClassLoader method in the same white-paper will likely produce a smaller client than the
          > > verboseTozip method - perhaps at least half the size.
          > >
          > > The next release of WL (unofficially 7.1) will include the long-awaited pre-packaged thin JMS
          > > client. (Yes finally!) Really really. I think the beta is scheduled to be out before the
          > > end of the year (sorry I can't give out the planned dates - I don't know if they are public
          > > yet.)
          > >
          > > Currently, I think the smallest J2EE style applet client can be achieved by proxying JMS calls
          > > via an EJB, where calls to the EJB are made via the JVM's built-in IIOP client.