Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread Igor Vaynberg
you simple need to change where the entitymanager instance lives, and control it via cdi conversation api. no need to expose any more of the jpa stuff. -igor On Wed, Mar 5, 2014 at 9:06 AM, Chris Snyder wrote: > Thanks, Igor - that's very helpful. Not sure how I missed that article > while I was

Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread Chris Snyder
Thanks, Igor - that's very helpful. Not sure how I missed that article while I was searching. It would be a bit tricky to implement in my situation (as I described in another response, the JPA implementation of the data storage is abstracted behind a service API), but I could make it work - perhap

Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread Igor Vaynberg
have a look here: https://www.42lines.net/2011/12/01/simplifying-non-trivial-user-workflows-with-conversations/ -igor On Wed, Mar 5, 2014 at 3:47 AM, Chris Snyder wrote: > I'm dealing with an issue that I'm sure has been solved by many people on > this list, but I'm struggling to ascertain the

Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread Chris Snyder
Hi Haiko, Thanks for the response. You raise some good points - it certainly would be cleaner and easier to understand. It also could be better for my layout, given the way I've organized the code: The data layer is abstracted behind a service API, so we could plug in a different storage engine (C

Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread Chris Snyder
Hi Patrick, Thanks for the response. does the Guice's PersistFilter really automatically find and re-attach > the backed object in the request while leaving the in-place-edit situation? Guice doesn't do anything with whether the objects are attached - I'm simply never detaching them (unless I i

Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread Patrick Davids
Hi Chris, does the Guice's PersistFilter really automatically find and re-attach the backed object in the request while leaving the in-place-edit situation? I thought... as long as "nothing"/nobody finds and re-attach the backed object, your changes are "naturally" temporary and only stored on p

Re: Best practice for updating JPA object without persisting changes

2014-03-05 Thread haiko
Hi Chris, I would go for option 4. This is how I implement such cases. It has an explicit distinction between states 'previewMode' and 'commited Mode'. Looks like more coding, but actually is clear about distinction between preview and saved. And that would help the programmer that picks

Best practice for updating JPA object without persisting changes

2014-03-05 Thread Chris Snyder
I'm dealing with an issue that I'm sure has been solved by many people on this list, but I'm struggling to ascertain the best way to solve it. I'm working on implementing in-place-edit functionality for some of our site content. The content is stored in a database and mapped via JPA. The edit form