Thanks!
On Apr 16, 6:46 am, Thomas Broyer t.bro...@gmail.com wrote:
Annotating your classes/fields/accessors is not enough; you need a tool that
uses those annotations. gwt-servlet-deps only contains the javax.validation
annotations, not any actual validator.
Try adding
Just in case: I suppose you have some JSR 303 validator (hibernate
validator, for instance) in your classpath?
If you see the Unable to initialize a JSR 303 Bean Validator log in the
console, then it's not going to work, as it simply won't validate anything.
--
You received this message
I dont use Hibernate, just JDO and the javax.validation annotation
classes that came with
gwt-servlet-deps.jar which I already included in my classpath. Am I
supposed to use another
library? I dont see any Unable to initialize a JSR 303 Bean
Validator errors on my console
either.
On Apr 15, 5:36
I meant, I just use plain appengine via JDO.
On Apr 15, 6:11 pm, Owen Ilagan oila...@systemacorp.com wrote:
I dont use Hibernate, just JDO and the javax.validation annotation
classes that came with
gwt-servlet-deps.jar which I already included in my classpath. Am I
supposed to use another
Annotating your classes/fields/accessors is not enough; you need a tool that
uses those annotations. gwt-servlet-deps only contains the javax.validation
annotations, not any actual validator.
Try adding hibernate-validator.jar in your classpath, and see if it makes a
difference (I bet it will)
Hi!
So I finally got Request Factory to work on my Eclipse environment and
I'm trying out the Entity validation features. Following the example
on the tutorial, I add @NotNull to my Entity class property like so:
import javax.validation.constraints.NotNull;
@Entity
public class Employee {
