Well, you can specify your own config objects on some struts-config.xml elements at deployment. Couldn't you write a config object that handled the required behavior internally?I do not want to change the configuration for all time. I alway want to suggest at initialisation that object class B should be used instead A and do that programmatically.
For 2.0 we should look at the config subsystem and maybe define them as interfaces and use a factory to get the implementation class. Then, maybe instead of specifying config subclasses in struts-config.xml we would specify the config factory to use. IMHO, this would make the configuration much more flexible.
David
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
