Yunfeng Hou <houyunf <at> yahoo.com> writes: > At runtime, the tapestry servlet will create a context > class loader with all these archives included, and all > pages or components created by the servlet can have > the correct classpath.
-1 to more classloader tricks. These component jars could be loaded from WEB-INF/lib as everything else -- The tapestry runtime would look for something on MANIFEST.MF or some other configuration file to figure out libraries. Proposal: component jars could contain something like this on MANIFEST.MF Tapestry-Component-Library: contrib;org/apache/tapestry/contrib/Contrib.library i.e, for each component library, the MANIFEST should contain a Tapestry-Component-Library attribute. The value of the attribute should be the namespace, followed by a semicolon, followed by the path to the library specification. At runtime, Tapestry would load all MANIFEST.MF files, and check if any of them contains Tapestry-Component-Library attributes, and automatically add any libraries found to the current application. -- Marcus Brito --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
