I'm running with an older WildFly configuration (EE TCK) that probably doesn't have the needed changes for the "jboss.clustering.registry.ejb.default" service. Rather than just syncing up with the WFLY-3175 changes, I would like to know if the dependencies on "jboss.clustering.registry.ejb.default" should be optional so that people with older WildFly configurations do not get service dependency errors on "jboss.clustering.registry.ejb.default"? Scott _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Test configuration file that I'm using is available at https://www.dropbox.com/s/3yedst8yuobhruu/standalone.xml if that helps. On 04/09/2014 09:14 AM, Brian Stansberry wrote: > If that change breaks existing configs, it's a major problem. For sure > it has to be corrected for 8.0.1. We can't break existing configs in a > bug fix release. > > On 4/9/14, 7:07 AM, Scott Marlow wrote: >> I'm running with an older WildFly configuration (EE TCK) that probably >> doesn't have the needed changes for the >> "jboss.clustering.registry.ejb.default" service. Rather than just >> syncing up with the WFLY-3175 changes, I would like to know if the >> dependencies on "jboss.clustering.registry.ejb.default" should be >> optional so that people with older WildFly configurations do not get >> service dependency errors on "jboss.clustering.registry.ejb.default"? >> >> Scott >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> > > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev