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.
Since you're running in the same JVM, I'm not sure why you
can't set up some sort of observer-subject scheme (kind of
like ActionListener if you're familiar with that) so that the apps
can just access each other's object directly. You can set up a
singleton object to register the observers between webapps.
Just be sure to synchronize properly.
It should be pretty simple to do and dramatically more efficient
than RMI/SOAP or really anything over an IP connection. It's
hard to beat direct memory access for speed.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
