Action beans should/must be "prototype" scope ?

[Tom Zeller]

> I guess you are implicitly saying we can't use it literally the way
> Spring wants to because we don't want to do component scanning, etc?  Or
> else we know that that doesn't combine with XML-declared beans?

Yes to the former, we are avoiding annotation-based container configuration.

(That is a short sentence we could talk about for a while ;-)

> If so: Perhaps we could still make use of a BeanFactoryPostProcessor to
> implement the @Scope annotation in a different way than
> component-scanning, by using it to directly set the scope on the bean
> definition.  I haven't tried this, so don't know if works.

I have not tried a PostProcessor nor plan to anytime soon, would be
good to know if that works.