Feb 11th, 2007, 09:36 PM
web application communication, lazy loading and service discovery
We have two web applications (App1 and App2) that need to talk to each other and at the moment we're planning to use RMI spring remoting. The problem is since we're dealing with web applications, we have no control which application starts first. App1 needs to act as the remoting server and App2 as the client. If App2 starts before App1 then an exception will be thrown saying "connection refused" since the remoting server hasn't started yet.
Is there a way to configure these remoting services to facilitate lazy loading or service startup discovery?