Smells like a webservice classic. You can use a webservice to do the "high level" talking. Then use Apache Axis to implement it. That gives you the freedom to choose whatever mechanism fits best for the actual connection. It would allow for a in memory transfer if you are in the same jvm or a full fledged ws call when on different physical machines. Axis hides that from your apps.
Hth :-) stw "JWM" <[EMAIL PROTECTED]> wrote on 22/11/2005 08:03:45: > I understand the architecture of webApps is that they are intended to be > self-contained and not aware of other webApps in the system. However, I > have two loosely-coupled webApps that periodically need to crosslink to each > other. I have some relatively heavyweight objects that I would like to pass > from one webApp to the other. Since the session objects are different for > the two webApps, that let's that out. I know I could serialize the object > and use the database, filesystem, or even pass it across as a form > parameter. But that will be a performance nightmare and will require > periodic cleaning after sessions go away. And it just seems like overkill > to simply get an object passed within the same JVM. Combining the webApps > into one is not an option either. > > First question is whether there is some architected way to pass a java > object from one webApp to another (same user logged on via single signon). > In lieu of that, is there some sort of "you really shouldn't do this, but if > you must... here's how..."? Or am I stuck with db, filesystem, cookie, etc. > approach? > > Thanks. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
