I'm just taking a guess here, but I think it won't. As far as I know
the tapestry spring integration was always limited to singleton beans.
I think the "prototype" variant is maybe difficult to handle since
tapestry ioc (and hivemind in the past) have a somewhat different
approach on object creation, using pooling and all, afaik.

I never really considered that a big drawback, though. Plus,
apparently you can just inject the application context and get your
prototype beans from there. See
http://tapestry.apache.org/tapestry5/tapestry-spring/ , last sentence.

Hth,

Lutz



On Sun, Sep 14, 2008 at 6:17 PM,  <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I noticed in the documentation that non-singleton beans are not handled 
> properly, will this be fixed before the official release of T5?
>
> Regards,
> Amir
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to