> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Friday, 24 October 2003 11:45 a.m. > To: [EMAIL PROTECTED] > Subject: Re: Design question with Struts > > Shane, > > In this particular application, yes that is exactly what it does. I don't > need any modifications that span multiple requests in this particular app. > <snipped> .... </snipped>
> This type of system doesn't work for everything, but it does for a lot I > have found. Large scale GIS systems I am pretty confident it wouldn't work > well in, for instance. > > Does that clear up what I described? > Yes it does :-) And answered more. Thanks. I am currently developing a Struts/OJB app and have not yet nutted out the architectural issues/design ... have been reading Core J2EE Patterns and Patterns of Enterprise Application Architecture. OJB caches a read object so that I do not wish to pass that actual instance up to the View layer for editing ....IOW that instance only changes when an updated version is persisted. So in essence I need to create a session copy of my domain model from its persisted state to be available for editing (business transactions). But as this is a object with a collection of other editable objects it seems that creating a type of Value Object or session copy is not that trivial. Cheers Shane --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
