Home/ Questions/Q 7441913
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T11:05:35+00:00

I’ve just started using Java EE recently to build webservices. Most of these have

  • 0

I’ve just started using Java EE recently to build webservices.
Most of these have been very simply in that they get a request, do some work, and return a result. Once the result is returned to the client it dies.

Now I need to be able to respond to the client, to indicate that it’s request has been received and that it is being processed, but I don’t want to end the webservice thread after sending the request. I need it to do some processing after responding like sending requests to other webservices. The client will then routinely poll to get the outcome of the result. This will be handled by another webservice call thread.

I’m not sure if this is possible in Java EE. I’ve generally only done this using xml of TCP sockets.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Starting with Java EE 6, it’s possible to define EJB’s methods as asynchronous: see Asynchronous Method Invocation. So your routine would be calling an asynchronous bean from the bean handling your web service, to trigger the start of your lengthy process, and returning to the client. You can then query the result of this process through a different web service method.

    In Java EE 5 it’s also possible, though not directly, but utilizing timer tasks. It is, however, not possible to query the result of such task automatically, so you’d have to design it so that it saves its state in a database, from where another bean could read it.

    • 0