Re: Receiver method onConstraintViolation not called

2013-03-24 Thread Thomas Broyer
On Sunday, March 24, 2013 2:50:59 PM UTC+1, Nils wrote: > > Hi, > thanks for your reply. > All my session beans are stateless and i'm using a persistence unit with > jta-transaction and hibernatePersistence provider. > I didn't change the transaction attribute, so it should be 'required' by >

Re: Receiver method onConstraintViolation not called

2013-03-24 Thread Nils
Hi, thanks for your reply. All my session beans are stateless and i'm using a persistence unit with jta-transaction and hibernatePersistence provider. I didn't change the transaction attribute, so it should be 'required' by default. I also don't call transaction methods explicit. Please correct

Re: Receiver method onConstraintViolation not called

2013-03-24 Thread Thomas Broyer
See https://code.google.com/p/google-web-toolkit/wiki/RequestFactoryMovingParts#Flow for the flow on the server-side. Notably, validation shouldn't happen in a transaction. How are managing your sessions/transactions? What are their respective lifetimes? On Saturday, March 23, 2013 7:38:15 PM

Receiver method onConstraintViolation not called

2013-03-23 Thread Nils
Hello, any ideas why the Receiver method onFailure is triggered instead of onConstraintViolation when validation fails on server side? I just have to annotate the entities in my ejb module right? I'm using RequestFactory for communication with server. On server side i'm getting a rollback excepti