Design Issue with using MDB

Question

Lack of timer services with EJB 2.0 dictated our design to implement MDB, since we really needed to use a timeout mechanism for the calling client. Client puts requests into the queue and after processing, the response object messages are put into the response queue owned by the client i.e client configured queue on the JMS server. This model works for the case where the client is a stateless session bean. Now the issue is that we having another client - web application this time, with a servlet pumping requests to the request queue . How do I retain the same model but send queued messages back to the web application? since a response queue cannot be owned by the app. or can it? is there a work around for this scenario..anyone faced a similar situation?

Answer 1

May be I was not clear enough in my first explanation, Let me try again to explain my scenario:
My Expectation from Multi Provider is :
IObjectA
1AAA
(From InfoObject)
Union
IObjectA     IObjectB     IObjectC
1AAA     2BBB     3CCC
(From Cube)
The record in the multiprovider should be :
IObjectA     IObjectB     IObjectC
1AAA     2BBB     3CCC
Because, this is what the Union says .. and the Definition of the multiprovider also says the same thing :
http://help.sap.com/saphelp_bw30b/helpdata/EN/ad/6b023b6069d22ee10000000a11402f/frameset.htm
Do you still think this is how the behaviour of the multiprovider.. if that is the case what would be the purpose of having an infoobject in the multiprovider.
Thank you very much in advance for your responses.
Best Regards.,
Praveen.