"mark.little(a)jboss.com" wrote : Stepping back a moment: what's the estimate of time and effort to change the current configuration approach used by GpListener and friends? I'd guess this is what we're talking about: 1. Change GpListener to get PM to read load the config (instead of DomElement) 2. Change all code in GpListener that access GpListener config params + Listener wiring config 3. Change all Listeners that access config params through DomElement 4. Change the ActionDefinition code to access ActionProcessor wiring config info through 5. Changing all the unit and QA tests 6. Changing the Trailblazer Hmmm, I wouldn't be surprised if you had little/no change left out of 7/8 days to be honest. I suppose one could bull into it and get it done quicker, but I'd bet they and others would be dealing with that for weeks after. "mark.little(a)jboss.com" wrote : Time is of the essence here, so something very invasive may not be the best approach until after the RC. +1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978562#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...