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
on 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
>> or perform
ly using transactions?
>
> If so why not modify the interceptor to only commit if a SUCCESS is
> returned
> or perform a rollback if ERROR is returned from the action invocation.
>
> Al.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
9290
>
> Fort Collins Science Center
> US Geological Survey
> 2150 Centre Ave, Building C
> Fort Collins, CO 80526-8116
>
>
>
> "Al Sutton" <[EMAIL PROTECTED]>
> 10/02/2007 12:14 AM
> Please respond to
> "Struts Users Mailing List"
>
uot;Struts Users Mailing List"
To
"'Struts Users Mailing List'"
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 SU
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
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 Collection getAllProjectTypes(){
return this.projectTypeDao.getAll();
}
Notice that instead of returning a simple
7 matches
Mail list logo
