Ideally, your state objects should be as simple and small as possible
-- if for no other reason than to make sure your app can cluster if
required. Also, if you're using a service then you're probably
performing business logic and a state object is probably not the best
place for this. I'm
We've got an application state object into which we're injecting some
beans from Spring. Over time we've tried a number of approaches to
this.
Under Tapestry 3, we'd cobbled this together with some code in a
pageBeginRender() listener in a base page class. The pages had access
to the Spring con
