DWR is running in the web-tier
whereas MDBs run in the EJB tier. It's probably easiest to have a JMS
service running in the web tier using something like Spring JMS instead
of using an MDB
(http://www-128.ibm.com/developerworks/web/library/wa-spring4/).
Cheers,
Lance.
dio wrote:
Is there any update for JMS usage with DWR? Basically my question; is it
possible any DWR POJO can pass the caller page/session context to JMS
Message Driven Bean by sending a messaeg to JMS queue and MDB can return the
result to to caller HTML page when finish processing by using passed by
using the sent page util. Thanks
chago wrote:
Thanks, that is good to know. I'll take a look at the open-ajax hub and
see if I can get Active MQ supplying it with feeds.
Is there a mailing list for the hub? I'm curious to know if it is the
hub's responsibility to support the request-response metaphor, or will
that still be the responsibility of the client javascript?
-- jim
Joe Walker-3 wrote:
JMS is absolutely on the plan.
The idea is to be a JMS provider on the server and an open-ajax hub
plug-in
on the clients, so you can get a federation of pub/sub providers.
You can make DWR use less connection time by configuring it to polling if
you want.
Joe.
