I've read 13.7 in the ref, and the approach to integrating Tapestry with Spring sounds very cool.
Why not just initialize the appContext in the custom Visit object, and expose beans via getter methods?
I've read 13.7 in the ref, and the approach to integrating Tapestry with Spring sounds very cool.
Why not just initialize the appContext in the custom Visit object, and expose beans via getter methods?
Answered my own question. Thanks anyway.
It would be very nice to have the sample Tapestry engine from the ref integrated into Spring. tapestry.SpringEngine.