> Having to set things back explicitly is very bad. You should _always_ set whatever you change explicitly! Silent changes will fail in most frameworks or distributed environments. If struts would show such behaviour you should report it as bug.
> Often the objects in > question are non-trivial and belong to and are manipulated by libraries > and components that have no knowledge of the servlet api. Im hoping > someone can give some advice on what sort of techniques we could use to > deal with such situations. The objects in question should be just Data Containers (beans) without any background logic (not DAOs). And they should be Serializable. In this case you will have no problems with clustering. As long as you hold your action forms in request scope, you shouldn't have any problems at all. Regards Leon > -----Ursprüngliche Nachricht----- > Von: Andrew Hill [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 16. Dezember 2004 06:21 > An: Struts Users Mailing List > Betreff: Re: ServletContext, Initialisation, & Distributed Environments > > <snip> > pick something from the scope and change it you have set it back > explicitly > </snip> > > Ive heard something similar too. Id quite like to hear from someone > (like Craig ;->) who can give a definite answer. > > Having to set things back explicitly is very bad. Often the objects in > question are non-trivial and belong to and are manipulated by libraries > and components that have no knowledge of the servlet api. Im hoping > someone can give some advice on what sort of techniques we could use to > deal with such situations. > > [EMAIL PROTECTED] wrote: > > > Hi, > > We had to check out some design issues because the client > wanted a > > clustered environment. We never tested it though. > > > > I know that if you pick something from the scope and change it > you > > have set it back explicitly. I recall that this is a requirement to > enable > > session replication in a cluster. > > > > So if I write Struts code that changes the ActionForms in the > scopes > > and don't set it back it will fail in a cluster. Is that right ? > > > > > > Mohan > > > > > > This message is for the designated recipient only and may contain > > privileged, proprietary, or otherwise private information. If you have > > received it in error, please notify the sender immediately and delete > the > > original. Any other use of the email by you is prohibited. > > > > > > > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the email by you is prohibited. > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
