Hi again! We are using tapestry 5.1.0.5, and by the moment, we can't change it.
We need some mechanism to know the previous page from any page. Therefore, we want to hide that the implementation is made with a sessionState object. So our idea was to save the sessionState object inside an spring bean. We decided to contribute with a service to the Tapestry MasterDispatcher by adding a new dispatcher (which acts before the PageRender dispatcher). Thus, in our dispatcher we injected a bean for carrying the SSO, but we had a problem by trying to access from different sessions. Even the id of the SSO was different, its content was the same for all sessions. Later, we tried to make that the bean wasn't a singleton bean, because we thought that the problem was related to the bean itself. However, this approach isn't useful for us because a new instance is created every time is requested, loosing the SSO. Finally, we decided to implement it as a SSO directly, but we would like to know if exists a way of using the bean. We hope for your answer. Regards. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Is-possible-to-use-an-spring-bean-to-carry-a-SessionState-object-within-a-dispatcher-tp4591010p4591010.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
