Re: Hibernate and S2

Jeromy Evans wrote: Mansour wrote: An alternative approach is that you don't allow persistent entities to be modified within your actions whatsoever and all updates are applied behind a service layer that performs reattachment and updates. How do I do this (reattachment and updates)? Assuming

Re: Hibernate and S2

Mansour wrote: An alternative approach is that you don't allow persistent entities to be modified within your actions whatsoever and all updates are applied behind a service layer that performs reattachment and updates. How do I do this (reattachment and updates)? Assuming I have a very big a

Re: Hibernate and S2

Jeromy Evans wrote: Let me re-articulate my interpretation of what you've done: You load an entity E with say 4 properties (a, b, c, and d) from persistence and render a view based on it. The persistence session is closed. In a new thread, the user submits an update that affects only two prop

Re: Hibernate and S2

Let me re-articulate my interpretation of what you've done: You load an entity E with say 4 properties (a, b, c, and d) from persistence and render a view based on it. The persistence session is closed. In a new thread, the user submits an update that affects only two properties of the entity

Hibernate and S2

Hello every one: This question may seem of topic. The reason I am asking this here is because I am sure some one faced this problem when dealing with struts and can provide an advice. I have many objects that are mapped using hibernate to a DB. I need to update one of these objects (lets call