XWork has a similar class, it is called XWorkConfigurationProvider. musachy
On Mon, Jul 27, 2009 at 11:31 PM, Lukasz Lenart<lukasz.len...@googlemail.com> wrote: > 2009/7/27 Musachy Barroso <musa...@gmail.com>: >> <constant name="struts.textProvider.class" value="mytextprovider" /> >> >> Then you register the bean in BeanSelectionProvider, like: >> >> alias(TextProvider.class, "struts.textProvider.class", builder, props); > > But this will work only for Struts and not for XWork where the problem > is, right? As I understand XWork first build configuration base on > XWorkConfigurationProvider and on any number of > XmlConfigurationProviders (one for each xml config file). And base on > that, the Conatainer is created with defined beans ready to inject. > So, the only option to override bean definition is to put it in > xwork-default.xml and remove hard coded factory from > XWorkConfigurationProvider? > > Or what is the difference between DefaultTextProvider (which looks > like it should be used only by Xwork internals) and > TextProviderSupport? Maybe all I need to do is to clean up such > separation of concern and make as musachy suggest? Anybody knows? > > > Regards > -- > Lukasz > http://www.lenart.org.pl/ > http://dailylog.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
