struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lukasz Lenart <lukasz.len...@googlemail.com>
Subject Re: Xwork injecting
Date Tue, 28 Jul 2009 06:31:52 GMT
2009/7/27 Musachy Barroso <musachy@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-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message