Nevermind. I guess I skipped pages 275 and 308 in TIA.
However anybody have any issues/experience using cgilib with tapestry? I remember reading somewhere that the proxies are not serializable as java.lang.reflect.Method is not serializable.
I was thinking of implementing a Proxy Pool that is created and filled on startup by all apps in the cluster. Then I would have to implement a factory to produce a Proxy from this pool to use on a domain object. This way I can simply wrap the proxy in a proxy holder and store the holder as a persistent property. For each request cycle the ProxyHolderlder will get a proxy from the pool and use it.
I know this is off my original topic but any comments/experienced advice would be much appreciated.
Thanks again
Doug
On Tue, 03 May 2005 08:14:41 -0500 "LOCHART,DOUGLAS E" <[EMAIL PROTECTED]> wrote:
We will be moving to a clustered environment for our application. We are/will be using Apache (SSL) (with distcache to handle load balancing with SSL), Tomcat with load-balancing/clustering and an encrypted postgres database.
We are using a simple home grown Data Access layer which I will be putting an interceptor/proxy layer in front of using CGLIB (thanks for the mini how-to Konstantin).
I have three questions:
1) When I save something or update something in the Visit object is it guaranteed to be updated in the Session object? You know the whole Object in the Session issue where in order to guarantee proper session clustering the setAttribute() on the session must be called and not just updating the object in the session.
2) Given that the whole Session is updated and available to a cluster what about persistent properties? Many of my pages use persistent properties. What happens when I am load balanced/failed over to another Tomcat in the cluster. The Session will be there but what about stuff pertaining to Tapestry?
3) In general are Tapestry apps clusterable?
Any and all help is appreciated. This is my first clustered app as well as my first Tapestry app.
Again thanks in Advance.
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
