I can't help but think that we can move away (but support of course) from our own xml format and use the metaclass one in one swell swoop.
Thats what we did in Loom and it works fine as long as you have something that will read in an xml document and convert it into a set of MetaCLass attributes.
Again, I think I see oppurtunity for bigger changes! We could get completely rid of our old proxy management code and recast it as utilization of some AOP or interceptor toolkit. That would completely integrate interceptor support as to "tacking it on". WDYT?
+1
How about this...we start another branch (so you don't need to miss your project deadline) that's a little more radical and weaves dynaop and metaclass right into the fortress core, then after that we look back and try and figure out a way forward. WDYT?
+1
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
