[ https://jira.jboss.org/jira/browse/JBMETA-171?page=com.atlassian.jira.plu... ] Alexey Loubyansky commented on JBMETA-171: ------------------------------------------ Meaningful difference is between the ordering of proxy-factory-config: Branch_4_2 <!ELEMENT proxy-factory-config (client-interceptors? , activation-config? , endpoint-interceptors? , web-class-loader? , JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , metadata (the same in both jboss_4_2.dtd and jboss_5_0.dtd) <!ELEMENT proxy-factory-config (client-interceptors?, endpoint-interceptors? , web-class-loader? , activation-config?, JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , I don't know for which reason. In Java proxy-factory-config is represented as org.w3c.dom.Element (so, no ordering is defined in Java binding). I am thinking of changing it back to the ordering as in Branch_4_2. Other changes are added comments for the child elements of cluster-config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira