> On Apr 16, 2015, at 7:06 PM, Brandon Gaisford <bgaisford(a)punagroup.com&gt; wrote: > > > If no one is actively working on WFLY-1192, I’ll give it a go. Not sure how quickly I’ll be able to turn it around. Sources appear to be under wildly-core. Let me know if you’d like to me to work on this. Sure, thanks for stepping up. One thing that's important though, is to avoid breaking compatibility. The cascade behavior should somehow be specified. Do you agree?

Sounds, great. Thanks, Brandon. I agree this sounds like something in WildFly Core, so I'm going to move this JIRA to the WFCORE project. On 4/16/15 8:11 PM, Brandon Gaisford wrote: > > Hi Jason, > > Yes, I totally agree. It’s going to take some effort on my part to understand this code. I think for this particular feature it would be best if I do some prototyping and then propose a formal design document to the team before proceeding. > > Brandon > > > On Apr 16, 2015, at 3:07 PM, Jason T. Greene <jason.greene(a)redhat.com&gt; wrote: > >> >> >>> On Apr 16, 2015, at 7:06 PM, Brandon Gaisford <bgaisford(a)punagroup.com&gt; wrote: >>> >>> >>> If no one is actively working on WFLY-1192, I’ll give it a go. Not sure how quickly I’ll be able to turn it around. Sources appear to be under wildly-core. Let me know if you’d like to me to work on this. >> >> Sure, thanks for stepping up. One thing that's important though, is to avoid breaking compatibility. The cascade behavior should somehow be specified. Do you agree? > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev >