Action beans should/must be "prototype" scope ?

[Cantor, Scott]

On 2/6/14, 2:13 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:

>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.

Yeah, my preferred model would be: checking for an annotation (Springs or
ours) declared on our base class in a bean factory post processor, with a
flag at runtime being a backup choice.

I don't think we want to do both, and I don't think we want to bother with
an annotation being checked by our own classes, it's just a more
convoluted way of having a flag.

-- Scott