i assume you are spawning a seperate thread so the call does not wait? you could return a remotesharedobject id which the client then listens to and when your 15 second process is finished set the data in there.
On 5/8/07, Austin Kottke <[EMAIL PROTECTED]> wrote:
Hi, I'm doing a remoting to call to a j2ee service. The service takes about a total of 15 seconds to run. The problem is the call is made, it executes the java call, but because the call is still processing there is no 'return' value to the remoting gateway so it gives me a Netconnection.call.failed status. Even though it successfully called the service. Any ideas? And then when the java call finally finishes and returns the status this doesnt show up in a responder object. There is no output as it seems like the connection stops waiting... Best, austin
-- j:pn http://www.lennel.org
