0 Replies Latest reply on Mar 20, 2007 7:29 PM by Ralph Perko

    trouble with Asynch

    Ralph Perko Newbie

      Hello,

      I am very interested in using the @Asynchronous and Event.raiseAsynchronousEvent functionality. However, its lack of access to the Conversation and Session scope is difficult to work around. The documentation states the following:

      We usually use an asynchronous call when we want to return an immediate response to the client, and let some expensive work be processed in the background. This pattern works very well in applications which use AJAX, where the client can automatically poll the server for the result of the work.


      This sounds great and is exactly what we want to do! A brief summary is as follows:
      1) A user does a search.
      2) When the user selects a search results it kicks off a conversation and several areas are initialized in respect to the selected search item via Event / Observer. Each Observer is in a stateful session bean with a conv. scope.
      3) We then access the data we need from each bean.

      I would really like to make these initialization routines async without doing some context gymnastics to get the results in the conversation scope. The doc I quoted suggests "polling" but unless we put the results in the business or application scope I don't see how it is possible. Please let me know if I am missing something here or if you may have any suggestion?

      Thank you.