Dave et el - I can only conclude that either something is severely lost in my understanding of a Struts2 ModelDriven action coupled with Spring3 and Hibernate/JPA. I have tried numerous configuration changes, annotations, etc and nothing has appeared to avoid allowing dirty data to make it to the database and I just cannot continue with this risk; it just jeopardizes integrity.
So unless someone can shed some light on my implementation, showing what could be flawed; then I need to go down a different path. I like the notion that the ModelDriven does a lot of the grunt work for me with respect of populating my entity based on form properties and keeps my action class very clean and free of form bloat; however I feel it puts some risks on the table which I could easily avoid by not allowing the framework to modify my persistent entity and force me to manage the copy/update of the entity accordingly when applicable. > -----Original Message----- > From: Dave Newton [mailto:davelnew...@gmail.com] > Sent: Thursday, March 10, 2011 10:40 AM > To: CRANFORD, CHRIS > Cc: Struts Users Mailing List; Maurizio Cucchiara > Subject: Re: RE: Re : Re : ModelDriven & Hibernate Entities > > On Thu, Mar 10, 2011 at 11:38 AM, CRANFORD, CHRIS wrote: > > Yes the plugin is in the app's lib directory. > > Just FYI, that sets the object factory to "spring", so Spring is > instantiating your actions. > > (At least it used to.) > > Dave --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
