That's correct. I use @Connfigurable to inject spring objects into
tapestry pages. The downside is the need to include an xml bean
configuraion in spring for each page I want to inject to, although
I've been using the spring-annotation project to define the beans
using annotations rather than xml.
Daniel Tabuenca a écrit :
I think what you read there is not necessarily true. If you are using
Spring 2.0 and bean scopes or target sources then spring will give you
a proxy and automatically manage the lifecycle for you. Also keep in
mind that you can easily use spring itself to inject the bean
I think what you read there is not necessarily true. If you are using
Spring 2.0 and bean scopes or target sources then spring will give you
a proxy and automatically manage the lifecycle for you. Also keep in
mind that you can easily use spring itself to inject the beans into a
tapestry page by u
Hello,
I'm steel walking on the web to learn more about WebApplication with
Tapestry and other frameworks integration before starting to draw the
architecture of my future project... It's not so simple ;-)
Today I'm looking for Tapestry4 and Spring2.
On the site of Tapestry-Spring
(http://h