Just create a new CFC that extends ModelGlue.gesture.configuration.ModelGlueConfiguration, add your setConfig() function to it, have it's init method call super.init(argumentCollection=arguments) and return this, and then do this in your application's config/ColdSpring.xml file, in the modelGlueConfiguration bean section, in the class attribute, use your own class instead of the MG built-in one. Since you've extended the original it will work fine because the API won't have changed but for your added method.
It's so easy to override MG's built-in functionality I can't believe more people aren't doing it... I'm finding places for this constantly. :) J On Feb 9, 2009, at 11:50 PM, denstar wrote: > > On Mon, Feb 9, 2009 at 10:05 PM, Tony Nelson wrote: >> >> Or you could create a new config bean that extends the MG config >> bean. > > Or something like this: ... --~--~---------~--~----~------------~-------~--~----~ 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 . -~----------~----~----~----~------~----~------~--~---
