One question I had about these frameworks... Is it possible for me to define a default configuration, and allow the users of the framework to just selectively replace individual components, or would they have to reconfigure the whole thing?
Thoughts? Ideas?
One design that I'm beginning to see in some places, and which I just adopted for our own AOP framework, is to have the concept of a factory builder. I.e. one instance from which all factories are created. The benefit of this is that it becomes easy to centralize all factories, and replace them easily, and also ensure that all factories get along well.
Then, make one default FactoryBuilder implementation that provides the defaults, and allow users to subclass that and replace individual get*Factory methods with their own.
This makes all the factories a little more coherent, while still allowing for customizations.
/Rickard
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
