Action beans should/must be "prototype" scope ?

[Marvin Addison]

>
> But if we wanted to blow up and just insist that all actions be prototype,
> I wouldn't be opposed.
>

I'm fairly strongly opposed to that. There are many actions in the codebase
that are perfectly stateless and there's no reason to burn additional
object references on them. I would, however, be in favor of tightening up
our use of @ThreadSafe, @ThreadSafeAfterInit, and @NotThreadSafe and
possibly having some test coverage that ensures that beans bearing those
annotations have the appropriate scope in the bean container.

M <dev-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20151106/7a991d23/attachment.html>