Can you implement those as transient fields and reconstruct them as necessary?
I can see that having some non-servlet related class retain (and send messages to) your visit is also a problem. There are hooks in Tapestry for knowing when the HttpSession is invalidated (that is, ages out or explicitly killed), as which point you can unhook your visit from the other class. There aren't any notifications related to session clustering however. Are you sure you can't accomplish your goals by polling an object, rather than being a listener of the object? JBoss and WebLogic both support JMX. A JMX Bean may offer the correct lifecycle that you are looking for. I don't really have a magic solution; ultimately Tapestry is still hostage to the limitations of the Servlet API. -- [EMAIL PROTECTED] http://tapestry.sf.net > I'm implementing a web mail application. I need to keep some non > serializable objects (session scope) such as Store. In addition I need > a live object to be the listener of javamail events; for this case the > Visit object is not an option. > > I guess, Visit object is a general strategy to servlet clustering and is > really useful for application servers or servlet containers without > clustering support. As far as I know, WebLogic cluster is implementied > by replicating HTTPSession among application server instances. I'm not > sure about the extra baggage imposed by the Visit object for application > servers with clustering support. > > Is it possible to implement a kind of Visit object and store it in the > HTTPSession? > > > Any ideas? > > Regards ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
