Hi Fabiano,
first of all thank you for your valuable hint. I established an interceptor
CommitAwareInterceptor at the top of the interceptor stack. This interceptor
is tagging the JPA transaction for RollbackOnly in case of
a.) the action is not implementing CommitAware
b.) the action is
]
10/02/2007 12:14 AM
Please respond to
Struts Users Mailing List user@struts.apache.org
To
'Struts Users Mailing List' user@struts.apache.org
cc
Subject
RE: ModelDriven CRUD validation failure still causes JPA update -
RESOLVED
Just a thought, are you actually using
October 2007 04:04
To: Struts Users Mailing List
Subject: Re: ModelDriven CRUD validation failure still causes JPA update -
RESOLVED
OK: I've fixed the problem.
I'm not sure why this was the case, but here is what was causing the
problem:
In my ModelDriven action, I had a method like
@struts.apache.org
To
'Struts Users Mailing List' user@struts.apache.org
cc
Subject
RE: ModelDriven CRUD validation failure still causes JPA update - RESOLVED
Just a thought, are you actually using transactions?
If so why not modify the interceptor to only commit if a SUCCESS is
returned
Al Sutton [EMAIL PROTECTED]
10/02/2007 12:14 AM
Please respond to
Struts Users Mailing List user@struts.apache.org
To
'Struts Users Mailing List' user@struts.apache.org
cc
Subject
RE: ModelDriven CRUD validation failure still causes JPA update - RESOLVED
Just a thought, are you
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 02 October 2007 04:04
To: Struts Users Mailing List
Subject: Re: ModelDriven CRUD validation failure still causes JPA update -
RESOLVED
OK: I've fixed the problem.
I'm not sure why this was the case, but here is what was causing
OK: I've fixed the problem.
I'm not sure why this was the case, but here is what was causing the
problem:
In my ModelDriven action, I had a method like this:
public CollectionProjectType getAllProjectTypes(){
return this.projectTypeDao.getAll();
}
Notice that instead of
7 matches
Mail list logo
