I did not follow the thread completely, but AFAIK the original problem was that a session bean wants to asynchronously notify clients. "JMS Temporary Queue" seems to be a great idea, indeed, but how shall the session bean get that queue instance? Since the temporary queue gets created by the client, and since nobody guarantees that the vendor's implementation of the TemporaryQueue interface implements also the Serializable interface, one cannot pass that instance to the session bean. The samples in the JMS Tutorial only will work with MDBs since they take the queue instance out the JMSReplyTo header field -- but that approach is not possible here, since we do not have an MDB reacting to a queue, but a SB reacting to a remote method call.
So how shall that work?
Thanks
Markus
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Freitag, 23. Mai 2008 00:50
To: users_at_glassfish.dev.java.net
Subject: Re: How to invoke Client Callback Handler from EJB3 Session Bean
The formal term is "temporary destination".
This is a link within the JEE 5 Tutorial briefly discussing them. Crawl around from there to get the details.
http://java.sun.com/javaee/5/docs/tutorial/doc/bncfu.html#bncgb
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=276183
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net