First of all, I do net see that anybody attacked you. They just tried to
convince you that using JMS is the right approach, whereas callbacks
just will not work.
No, I do not know how the session ID can be obtain and just wait what
the Sun guys will answer on my question how to obtain the temporary
queue in the session bean. For an MDB, it is not a problem, but for SBs
it seems to be pretty hard to do. Current in my app I just am using a
global, persistent topic and do "broadcasts" from a session into the
topic using my own header field with a client ID. The client ID is
generated by random from the client and forwarded to the SB in the
constructor of the SFSB.
Regards
Markus
From: Miroslav Nachev [mailto:miro_at_space-comm.com]
Sent: Freitag, 23. Mai 2008 11:30
To: users_at_glassfish.dev.java.net
Subject: Re: Re: How to invoke Client Callback Handler from EJB3 Session
Bean
Hi,
Thanks that somebody support me because the guys from Sun attack me so
embittered. I am fully agree with you and that was the reason to ask the
community how to get the session key (session id) with which to create a
map between the session and client. Do you know how to get the session
key when I am in some Stateful or Stateless bean?
Regards,
Miro.
On Fri, May 23, 2008 at 11:10 AM, Markus Karg <karg_at_quipsy.de> wrote:
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