I discussed this with Mik and Jason at TSS Symposium but i just wanted to post it here so it doesn't get lost:
I thinke there might be an issue with the IoC approach when using Webwork in a cluster. As i understand it you can declaratively specify that an object should live in the Session scope, and then have an Action implement an *Aware interface so your Action gets the object from session set The problem is that in a cluster (alteast on Orion and Weblogic) you need to explicitly set the object back in the HTTPSession if it has changed, because the servers need to know when you have changed an object in order to notify other servers in the cluster (usually through multicasting). The simple solution to this is to explicitly set the object back in the HTTPSession after the execute() method is called. The overhead is minimal and it will then work in a cluster. sincerely morten wilken ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
