Darryl Pentz wrote:
I have an issue where webapp A needs to let webapp B know about an event, and
then return a response to webapp B's processing of that event to the browser.
So basically I need to communicate between webapps in the same container.
I have not found a no-brainer solution to this as yet. The one I have tried is
making a localhost HTTP call which I find to be rather expensive, given that it
requires creating a socket connection to the same container.
I also just encountered the 'crosscontext' attribute in the <context.../> block
and was wondering whether that could serve any purpose.
Does anybody know of any tried and trusted ways of communicating between
webapps in Tomcat?
Thanks,
Darryl Pentz
If you think that this thing will scale at all, steer clear of any
shared resources like JVM properties or magic files. It could be that
in the future the apps won't run even in the same network, much less the
same JVM. This is a classic SOA problem.
My $0.02:
If you're not transporting binary, might I suggest JSON? It's a whole
lot less painful to configure (no XML or schemas), and there are Java
JSON clients (jabsorb has one) that make it a snap to integrate into
your project. It just works like magic. We've been using it with our
projects for months now and are quite happy with it, both in terms of
performance and ease-of-use. JSON does use HTTP transport, so if you're
determined not to use HTTP, then it may not be for you.
Brantley
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
