It will JBoss AS 4.0.2 that is in sync with JBoss Remoting 1.0.1 beta (which should be out in March). I am hoping to have 1.0.1 final done and backported to 4.0.2 (which will be backwards compatible with 1.0.1 beta) The version matrix is at http://www.jboss.org/wiki/Wiki.jsp?page=Remoting_versions.
Until then, would have to build the server from jboss-head or the 4.0 branch.
Sorry. I just couldn't get beta done and backported in time. Please let me know if you have any other problems with this.
Thanks for your response Tom.
If I were to stick with remoting as delivered in JBoss AS 4.0.1, what would be the downside (as opposed to using the remoting 1.0.1beta)? I understand there are some changes around the transports that will be available in future?
My initial target implementation involves reasonably simple enquiry/response messages from a Java application to central server over public internet. Would I perhaps be better off using web-services in the short term?
Do you have a "quick opinion" on strategy for use of remoting vs. web-services?
Once again, many thanks for your help.
The remoting in JBoss AS 4.0.1 should work without a problem. However, the remoting version in JBoss AS 4.0.2 will be much easier to migrate to future versions of JBoss Remoting, as there has been some redesign between the two releases.
Web services is certainly a possible solution, but a little bit more difficult to get up to speed and use as the programming model is a little more complex. On the other hand, it is a standard. BTW, the new JBossWS (web services stack) sits on top of JBoss Remoting (but is not in 4.0.1 yet either). If have to stick with 4.0.1 for a while, would go with web services in that.
As some of this needs to be in production ASAP, I will probably go with JBossWS from 4.0.1 Seems like I need to be working with a bit too much beta/alpha code by the time I get all the dependencies resolved for remoting.
Hopefully have another look at remoting in a couple of months time.