If I'm not mistaken, the question was if the
ActionBeanContext.Classconfiguration parameter takes precedence over
classpath scanning. The answer
to that question is yes. This is true for all the various *.Classinit-params.
As Freddy pointed out, if more than one ActionBeanContext implementation is
found in your extensions package(s) and you do not configure
ActionBeanContext.Class in web.xml, then Stripes will throw an exception.
See BootstrapPropertyResolver.getClassProperty(String, Class) for the code:
http://stripes.svn.sourceforge.net/viewvc/stripes/trunk/stripes/src/net/sourceforge/stripes/config/BootstrapPropertyResolver.java?revision=1336&view=markup
-Ben
On Tue, Jan 25, 2011 at 9:22 AM, Freddy Daoud <xf2...@fastmail.fm> wrote:
> Nikolaos Giannopoulos <nikolaos@...> writes:
>
> > Would Stripes favor TLActionBeanContextTest
> > over TLActionBeanContext for
> > the ActionBeanContext???
>
> Hi Nikolaos,
>
> There is no "favoring" of one custom action bean context class over
> another. There should only be one, otherwise, Stripes will throw
> an exception on startup:
>
> "Found too many classes implementing/extending ActionBeanContext"
>
> Cheers,
> Freddy
>
>
>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users