Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: Piero Sartini <lists@pierosartini.de>
To: "Struts Users Mailing List" <user@struts.apache.org>
Subject: Re: ModelDriven CRUD validation failure still causes JPA update
Date: Mon, 1 Oct 2007 23:38:20 +0200
User-Agent: KMail/1.9.7
References: 
 <OFB042A4B7.C81016BA-ON87257367.00737537-87257367.0073E9E8@fws.gov>
In-Reply-To: 
 <OFB042A4B7.C81016BA-ON87257367.00737537-87257367.0073E9E8@fws.gov>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200710012338.20471.lists@pierosartini.de>

> Since my Model is acquired from the Hibernate session (during the
> "prepare()" Action method), it is a transactional persistent instance.
> Note this from the hibernate documentation:
>
> "Transactional persistent instances (ie. objects loaded, saved, created or
> queried by the Session) may be manipulated by the application and any
> changes to persistent state will be persisted when the Session  is flushed
> (discussed later in this chapter). There is no need to call a particular
> method (like update(), which has a different purpose) to make your
> modifications persistent."

I do not know hibernate but you could try the following solutions:

* don't flush the session and destroy the object

* instantiate a temporary bean used for the form only:
BeanUtils.copyProperties(tempBean, yourBean);

* manage your entities with JPA's EntityManager, merge them manually.

Piero

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org