I'd like to make a proposal to support JBoss tooling: Usecase: For examplea JMX and JNDI client that need to access different versions of JBoss servers.
Problem: 1.) The client libs for example between 3.0.6 and 3.2.0RC3 are incompatible. Accessing JMX for a 3.2.0 with client libs of 3.0.6 leads to an error and does not work. Something similiar applies to JNDI. A result of that is for example that MC4J does not work with 3.2.0RC3, other console tools for JBoss have different versions for different JBoss servers. 2.) Problem 1 is implementation related. Beside that there's no versioning for JBoss client libs in regard to interfaces. For example I can't be sure that RMIAdaptor has not changed unless I check the source code. Additionally it's not obvious what version of non JBoss client libs are provided with the JBoss client libs. For example is it JMX 1.0 or JMX 1.1. Proposed solution: The tools have to deal with client libs incompatibilities (i.e. via dynamic classloading). But there should be one tool section in the releasenotes. 1.) Stating whether the client libs have become incompatible to earlier versions. I don't want to extract this from the change section. It's important to have an explicit statement about compatibility. 2.) Stating what version of non JBoss client libs are provided with the JBoss client libs. Additionally there should be a versioning for JBoss specific client libs in regard to the interfaces and the version that is used should be mentioned in the tools section of the releasenotes. Closing: There are so many versions of JBoss servers. If tools want to support all of them reliably they need a "contract". Otherwise it won't work. Hans ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
