Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4F158FD7.2080203@baylishome.me.uk>
Date: Tue, 17 Jan 2012 15:12:23 +0000
From: Michael Baylis <maillist@baylishome.me.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: users@openjpa.apache.org
Subject: OpenJPA 2.1.1 and read entitys being marked as dirty
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Folks,
         I am experiencing an oddity that I can't google my way out of.

I am running OpenJPA 2.1.1 under Tomcat 7.0.23 by using my own 
EntityManager object that I create when the application starts.

What I am noticing is when I update a field in an entity and then commit 
the transaction,  all entities that I have read so far appear to be 
dirty and is updated in the backend database, even though I have not 
updated them.

I have performed further testing by amending a query to be surrounded by 
a begin() and commit() and the commit causes the db records to be 
updated even though I know that no updates have taken place.

I am obviously missing something in the setup that causes this, but I am 
at a loss to what.

If I run a similar query outside of a Tomcat servlet, ie in native Java, 
I don't seem to encounter this problem.

Any help in diagnosing this would be appreciated.

Cheers,

Michael