Well, the problem is really on the JMS implementation side. Correct
implementations of connection consumer should be appearing on the market
this year, but right now they are few and far between. At that point, you
should be able to take advantage of support for concurrency in application
servers. I don't know what other vendors are doing, but we've been
supporting MDBs since last September and we have code in place to support
the connection consumer interface. Others may be doing the same.
I'd caution you to stay clear of the RI as a learning tool for application
server integration with JMS. They essentially threw out Chapter 8 and came
up with a custom solution to get around certain deficiencies in the JMS
specification. This is a strange approach for an RI, I think, though they
have valid reasons for their design decision. In any case, I would imagine
that most vendors will steer clear of this approach in so far as they can,
so its utility as a learning tool is certainly diminished.
Greg
-----Original Message-----
From: cyrus brocha [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 13, 2001 8:34 AM
To: [EMAIL PROTECTED]
Subject: jms application server interfaces
Hey ! Greg,
yes ! you are correct that there is nothing
that prevents from doint that..
is anybody aware of any such implementations ?
may be for handling MDB stuff of EJB2.0..
is this the approach generally ppl take to
implement MDB ??
and for that the CONTAINER should maintain a
"list" of all the messsages it has got and then using
the ConnectionConsumer may be it will load the
sessions with the appropriate messages (after
unsetting the MessageListener with which it has got
the message) and then may be calls
ServerSession.start() on each one of them ....
will this approach work ??
if anybody has any better way then throw some
light on the same.
thanks in advance..
Regards,
Cyras Brocha
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.in address at http://mail.yahoo.co.in
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
