Ionel, The class loader for the applet engine handles the request for classes. If you want to streamline the size of the support jars, here are some tricks which might help.
1) clear your webserver's logs Remove the archive statements from your APPLET tags. expand the jars in the base directory for the applet. clear your browser's cache. access your applet with a browser and run all of it's functionality (every execution path) the resulting access log will show which classes are required by your applet to operate. use the list to create your own (hopefully smaller) jar file. It takes some time, but it will work. 2) Another option is to compile everything (including the JBoss classes) from source, starting from your applet code, using the -d compile option. If the code does not do any runtime class loading (Class.forName) then all the class files necessary should be in the output directory. Jar them up and use it as your archive. Hope this helps, Mike Hewitt -----Original Message----- From: Ionel Gardais [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 8:40 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] size of packages clients need to download HI, thanks for your reply. I don't know that much about on-the-fly class loading. Is it smart enought to know that if I load a class (A) that uses another class (B), it will load both class A and B ? thanks, ionel Lachezar Dobrev wrote: > You can always decompress the jars on the Web-Server. > Then the classes will be downloaded on request, which will not lower down >the download size (it is getting bigger), but will make asynchronous class >download available. > I.E. The Applet loads some boot-classes to run the applet. When there is >need to get the JMS classes it will query the server for these classes. > This is best in case that you use limited J2EE functionality (as you >mentioned just JMS) but don't know which classes are required. > > Reffer to the HTML Applet tag documentation on how to set up the directory >styructure for that. > > lachezar > >>Hi, >> >>In an Applet framework unsing the JMS, there are 6 packages to download >>(jboss-common-client.jar, jbossmq-client.jar, jnp-client.jar, log4j.jar, >>concurrent.jar and jboss-j2ee.jar) plus the needed classes for my app. >> >>Its then a "little" 940kb to be downloaded by the client. As some users >>have slow connection, is it possible to decrease this amount ? >> >>I'm using JavaWebStart for another project but I'd like this one to be >>100% web available. >> >>thanks, >>ionel >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>JBoss-user mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-user >> > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
