sage in context:
http://www.nabble.com/ModelDriven-CRUD-validation-failure-still-causes-JPA-update-tp12987242p21062748.html
Sent from the Struts - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr...
ervices
>> ECOS Development Team
>> [EMAIL PROTECTED]
>> 970-226-9290
>>
>> Fort Collins Science Center
>> US Geological Survey
>> 2150 Centre Ave, Building C
>> Fort Collins, CO 80526-8116
>>
>>
>>
>> "Al Sutt
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
e Ave, Building C
Fort Collins, CO 80526-8116
[EMAIL PROTECTED]
10/01/2007 08:29 PM
Please respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
Unfortunately, it app
ase respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
Only difference is that I don't use model driven. Is there any setting
to tell hibernate to flush the session when c
rs Mailing List
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
--- [EMAIL PROTECTED] wrote:
> That's an interesting idea Dave. I'm using the
> paramsPrepareStack. It'll take some investigation to
> see if that would fix the issue.
Shouldn&#
ASRC Management Services
> ECOS Development Team
> [EMAIL PROTECTED]
> 970-226-9290
>
> Fort Collins Science Center
> US Geological Survey
> 2150 Centre Ave, Building C
> Fort Collins, CO 80526-8116
>
>
>
> "Musachy Barroso" <[EMAIL PROTECTED]>
IL PROTECTED]>
10/01/2007 05:10 PM
Please respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
I only use the beanutils.copy solution on a few places, on the other
cases I a
e Ave, Building C
Fort Collins, CO 80526-8116
Piero Sartini <[EMAIL PROTECTED]>
10/01/2007 03:38 PM
Please respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
&
I only use the beanutils.copy solution on a few places, on the other
cases I always load the object model on the prepare() method if the
"id" field is set (editing), and then call update or create on the
entity manager in my action method. I never got that problem so I'm
wondering what is different
--- [EMAIL PROTECTED] wrote:
> That's an interesting idea Dave. I'm using the
> paramsPrepareStack. It'll take some investigation to
> see if that would fix the issue.
Shouldn't take much; it might be as simple as adding a
validate/defaultWorkFlow up towards the top (although
I might try just add
cal Survey
2150 Centre Ave, Building C
Fort Collins, CO 80526-8116
Dave Newton <[EMAIL PROTECTED]>
10/01/2007 03:32 PM
Please respond to
"Struts Users Mailing List"
To
Struts Users Mailing List
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
I
> * instantiate a temporary bean used for the form only:
> BeanUtils.copyProperties(tempBean, yourBean);
>
That's what I do.
musachy
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
-
To unsubscribe, e-mail: [EMAI
> 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
CO 80526-8116
>
>
>
> "Musachy Barroso" <[EMAIL PROTECTED]>
> 10/01/2007 02:42 PM
> Please respond to
> "Struts Users Mailing List"
>
>
> To
> "Struts Users Mailing List"
> cc
>
> Subject
> Re: ModelDrive
:42 PM
Please respond to
"Struts Users Mailing List"
To
"Struts Users Mailing List"
cc
Subject
Re: ModelDriven CRUD validation failure still causes JPA update
If there is a validation error the code on your action shouldn't be
executed at all, so you wouldn't hav
If there is a validation error the code on your action shouldn't be
executed at all, so you wouldn't have this problem. Are you applying
the "defaultWorkflow" interceptor to your action?
regards
musachy
On 10/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have a ModelDriven action which c
I have a ModelDriven action which controls CRUD operations on JPA managed
Entity E. E has a property called ?name? which maps to a database column
with a NOT NULL constraint. I have added a RequiredStringValidator
annotation to my Action to validate that the ?model.name? property is
non-null. T
21 matches
Mail list logo
