There's documentation on the Wiki about integrating Tapestry and Spring.
Once it's done, it looks like:
@InjectObject("spring:MyBean")
public abstract MyBean getMyBean();
// or <inject property="myBean" object="spring:MyBean"/>
This generates a read-onlyl property on the page/component for
accessing the named Spring bean.
On 7/22/05, Serge Eby <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What's the best practice for accessing Spring beans
> from classes other than pages and components?
> These beans were successfully injected in the page.
>
> TIA.
>
> --
> Serge
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]