Hello Ovidiu.
I've looked over the remoting stuff. Which Handler(s) do you expect to have,
and how many?
Will you expose the JMS facade directly over the remoting API (i.e. use a
Remoting Client to use JMS) or are the remote handlers just for JMS-JMS
communication? As in, between servers that
This thread continues at
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870417#3870417
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870418#3870418
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870418
Actually, above you say:
As for the communication between remote clients and server peers, I will use
Tom Elrod's Remoting.
So it seems that the Remoting is just for clients wanting to use Messaging
outside of the JMS API? Or will you create a JMS client as well?
View the original post :
Remoting is used behind the JMS API.
Use case:
Your client code looks up a ConnectionFactory in JNDI and it uses it to create
a Connection.
The ConectionFactory implementation (which delegates to a dynamic proxy) will
use Remoting to connect to a server pair, which will create a
So nice of you to pitch in!
The Messaging Core (even it it can use a lot of refactoring and addition of new
features) is not the highest priority right now. The critical part, at this
moment, is the JMS facade. Once it is done, it will allow us to release an
alpha, which people can download
