While the size of the full WebLogic JAR may not be a problem when you run server-side applications, it does cause a very large footprint for enterprise-level client-server applications that may be running thousands of clients. Having to deploy the full 20+ MB weblogic.jar file along with a client application can significantly increase the size of the deployed application, possibly making it too big to be practical, as is the case with a Java applet-based client program.
At around 400 KB, the JMS thin application client (wljmsclient.jar) file provides a much smaller client footprint than the full WebLogic JAR, by using a client-side library that contains only the set of supporting files required by client-side programs. The JMS thin client also requires that you use the standard WebLogic thin application client (wlclient.jar), around 300 KB, which contains the base client support for clustering, security, and transactions.
|