Difficult to update clients to new vesions of JBoss Messagin

[xkong]

To update to a new release of JBoss Messaging we are required to update jboss-messaging-clients.jar on client sides for every new release. For my case, I have near 100 client applications subscribe to topics on my jms server. It is very difficult to update client side configuration each time. I am wondering it is really necessary to change the file version number for each release? Can we have more loosely coupled client side interface? Or is there another way to work around this issue? Thanks.

[clebert.suconic]

From 1.2.0.GA and 1.2.0.SP1 we have everything compatible.
We are keeping the binary protocol compatible between versions after 1.2.0.

[xkong]

I used jboss-messaging-clients.jar of 1.2.0.GA to call configuration of 1.2.0SP1 and I got following error.

2007-04-03 10:08:41,318 ERROR [org.jboss.remoting.transport.socket.ServerThread] - Worker thread initialization failure
java.io.IOException: Can not read data for version 22. Supported versions: 1,2
 at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:649)
 at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
 at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:363)
 at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)

[ovidiu.feodorov]

Clebert

The compatibility tests must be run on release. This is how you know that stuff is actually compatible.