I think he was thinking you could use AOP to trap a call to setConfig() and use it to simulate the existance of a real method... but I don't think that would actually work.
Doesn't a method have to exist for AOP to actually do anything though? I haven't used AOP a lot but I would have guessed that it won't work without the method actually being there in the first place. Considering how easy it would be to just build your own config bean that extends modelglue.gesture.configuration.ModelGlueCofiguration and then use the path to your own MGConfig bean in your CS.xml file, there just does't seem to me to be a reason to pull the 800lb gorilla into the mix. :) J On Feb 10, 2009, at 8:34 AM, Tony Nelson wrote: > > Where exactly does AOP come in? > > -Tony --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
