I've updated the Spring sample to show remote wiring between to two
Spring composite components (application contexts). I added a simple
socket-based remote binding to the test module which is used for the
wiring. The limitations of this binding are that service operations
must only take one parameter and be serializable. Error checking
isn't good yet in the test binding so be careful.
To get it running, build the spring client and server sample modules
and deploy the corresponding wars to a servlet container (both are
web apps). Then, go to the client test.jsp page to initiate the invoke.
Moving forward, we will need to do the following:
1. Substitute a real binding such as Celtix
2. Use Meeraj's war plugin to create the wars
3. For the server sample, I don't think we need to deploy it in a web
app. As an alternative, we can deploy it as a standalone jar, which
would show a more heterogeneous, service-oriented topology
Also, moving forward, once Andy's patch is in to integrate the Spring
web UI infrastructure, we can show a setup where Tuscany is less
invasive in a "pure Spring" environment.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
