The only two choices to perform inter-webapp communication is to place code in a shared classloader (such as Tomcat's common/lib directory), or use a wire protocol. The wire protocol will make a connection from one webapp to another based on port/url etc.
The Servlet specification has gotten more and more strict in this sense, because it is the only way to guarantee the promise of "write once run anywhere", and to improve the security of the web applications. Excalibur and company can help you organize components that can support either approach. To share the same code between two webapps in Tomcat, store the excalibur components in common/lib and access them through the JNDI lookup (NOTE: declare it in the server.xml and reference it with a reference-link in the context.xml). To have two webapps respond to commands over a wire protocol, may I suggest using a RESTful approach. In that case using Excalibur doesn't really buy you much. On 2/21/2007, "Angel Todorov" <[EMAIL PROTECTED]> wrote: >Hi All, > >I stumbled over the Excalibur project while googling - is it possible >to use it in order to achieve inter webapp communication in a servlet >container such as Tomcat, without having to put all jars that the two >webapps use in a shared dir (i.e. shared classloader) ? > >Thank you in advance. > >Best, >Angel > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
