Hi to all, just a quick idea to minimize the overhead by pivot jars in a webapp:
I'm thinking on writing a simple servlet that (mapped on a dedicated URI, like lib-shared) publish the required jars to clients, but having them under WEB-INF/lib ... ok ok, many security problems could happen, but doing all thing right (like publishing only some type of resources, and only from some folders, requiring authentication, etc) could help to move also pivot jars with all server-side jars already under WEB-INF/lib , or shared lib (available in some application servers). In this way, webapp containing one or more Pivot webapps could be a little lighter (less MB of WAR), and many times I've seen "simple" Applets (from many commercial products) depending on many jars, like Spring, Hibernate etc ... Probably Pivot projects (and in this case, web-server) are not the best place for this type of component, but what do you think ? Could be useful, or is another my crazy idea ? Bye, Sandro
