This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am working on a desktop swing application. The application uses a lot of jars. I am using a whole lot of apache jars, itext, swingfx, etc etc. At the moment when I deploy the application there are a total of 60 jars. Is there a problem if I keep adding more jars into a project? Will this slow down anything? I was thinking that jvm should be able to handle any number of jars. After all it will load a class and once there are no more instances (or at some time the JVM thinks fit) it will unload the class. So it should only be a problem when the JVM needs to search a huge number of jars to load a class. Is this true? I am just rambling..
The bottom line is, is there anything defined in any spec regarding the maximum number of jars (or classes) an application should have after which things will start getting really slow.
Somebody asked that question not long ago. It's always a good idea to keep the resources required for an application to a minimum, but our conclusion, I believe, was that the classloading mechanism slowed that much by having extra jars.
Customer surveys are for companies who didn't pay proper attention to begin with.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: How many jars to use at the maximum for a swing deployment