What's wrong with providing instructions to the customer on how to install the "plugin" with a particular web app?
-----Original Message----- From: Goren Il [mailto:gore...@hotmail.com] Sent: Monday, July 05, 2010 2:44 AM To: users@tomcat.apache.org Subject: How to call an external class from a webapp (i.e. - implement a plugin) I would like my webapp to call an external class, which will be provided (as a name) in an XML file at run time. The external class will be developed by 3rd party, and might include additional JARs. I will refer to the external class and JARs as the "plugin". My webapp is provided as a WAR, so it is not possible to add the plugin into the same WAR (unless the customer performs it himself). I do not want to put the plugin's JARs in the common lib of Tomcat, so that it will not affect other webapps (the plugin might include JARs of different versions than the webapps use). I considered putting the plugin in a separate folder, and implement my own class loader that will look at that folder as well. It seems like too much of an effort for a simple task. What is the recommended way to achieve "plugin" capabilities for a webapp? Thanks G. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
