I had a similar problem. I fixed it by adding a dependency on the
Hibernate library hibernate-validator 4.1.0 to my project. I use ivy,
so I don't know how that works in maven. In ivy its:
<dependency org="org.hibernate" name="hibernate-validator"
rev="4.1.0.Final" conf="default" />
I found that the actual problem was caused by the annotation scan in
hibernate determining that the validator API was being used and
hibernate not being able to find a default annotation provider - which
is pretty much what Trevor says below.
Regards
Alan
On 5/11/2011 8:07 AM, Trevor Skaife wrote:
My guess is that because gwt is requiring the javax validation api
that hibernate then thinks you want to validate it's configuration
which then means you need the hibernate validator.
On May 11, 8:26 am, cruser<[email protected]> wrote:
Hi Juan,
Thank you for the reply
I am guessing you're referring to the pom.xml??? I am not using maven or any
dependency management tool. Do you know why these extra dependencies are
needed? My project works fine without these dependencies running GWT 2.2. If
I upgrade to GWT 2.3 then it breaks.
Anyone able to explain WHY it breaks?
--
You received this message because you are subscribed to the Google Groups "Google
Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
