> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 23, 2002 10:57 AM
> To: David Solis
> Cc: Tapestry Developer
> Subject: Re: [Tapestry-developer] Tapestry, HttpSession and WebLogic
>
> Can you implement those as transient fields and
> reconstruct them as necessary?
>
I could, but the creation is a time consuming process.
I'm looking for something like WOSession (WebObjects). WOSession has
similar goals to HttpSession.
Fortunately HttpSession is reachable from Tapestry classes.
> 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?
>
It could be a solution, but it could complicate the logic of the
application.
> JBoss and WebLogic both support JMX. A JMX Bean may
> offer the correct lifecycle that you are looking for.
>
I know nothing about JMX. Do you have a good reference?
> I don't really have a magic solution; ultimately
> Tapestry is still hostage to the limitations of the
> Servlet API.
>
This is the main reason because Tapestry is cool.
It seems to me you don't recommend storing objects in the HttpSession. I
guess the reason is clustering support.
My question is: Is it a good solution for WebLogic to use HttpSession to
store some objects?
I guess Tapestry stored nothing but the Engine in the HttpSession. I'm
not sure about the reason, for WebLogic, of using the Visit Object
instead of keeping objects in HttpSession. What do you think?
Thanks Howard
David
> --
> [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
