I've done something similar to this in Tapestry 3.
Let's say you have two apps: Catalog and Checkout, and that the user
is always sent to Catalog first. Catalog would then assign a "working
user ID", and dump its state to the database under that ID. When it's
time to go to the Checkout, use the External service to construct a
link with the working user ID and a full path to the Checkout
application. You can then make that a clickable link or redirect to
it -- the single redirection would contain the one think you need
(the working user ID) to pull info up from the database.
If the apps need to do more concurrent communication, Java RMI is a
possibility, but I suspect you don't need quite that much back-and-
forth.
...Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
