[jboss-dev-forums] [Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack

[palin]

Hi Richard,
I've just taken a look at both your private branch code and this post ;-)

"richard_opalka" wrote : 1.) Yes, the model of the SENDER and RECEIVER should be similar. I've just draw the client side, but you can imagine similar mechanism on the server side too. Just for clear in present I'm mainly focusing on the client side.
OK, as a matter of fact speaking of RM, client side and server side do a lot of things the same way. 

anonymous wrote : 2.) I was playing games and doing some experiments with JBossWS client side invocation framework and was looking for the most suitable place to put the RM SENDER in. I have implemented dummy sender and executed all the JBossWS tests on all JBoss AS version against this dummy sender. The result of my experiment is in SVN repository (in my branch).
  | You can find this dummy sender implementation in RemotingConnectionImpl.java.

But there's something that is not clear to me: let's consider the server side (but this also apply on client side), shouldn't the RM subsystem process incoming messages before passing them to the core? (for example to be able to send receive acks) As far as I understand, when you do all the RM processing in the RemotingConnectionImpl, all the core/application work has already been performed (you're ready to send response message, right?)

When working on ws-policy, we thought a bit about ws-rm too, since this is going to use policies. We immagined that we could have ws-rm handlers (set by the ws-policy deployer on both client and server sides) intercepting messages and passing them to RM subsystem. May be this is not the best idea... but you might consider this too ;-)

anonymous wrote : I'm expecting another questions, comments, criticism and opinions from you guys ;-)

Just an idea for now... this afternoon I was thinking about cluster with Stefano. Did you consider that a real reliable messaging system is most likely going to be deployed on a clustered environment? (I mean, if you're seeking for reliability... why having a single point of failure using a single host?) IMHO it might be a plus to design the RM implementation keeping this cluster-issue in mind.

Bye
Alessio Soldano

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086397#4086397

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086397