How to do validations in GWT MVP Pattern

72 views
Skip to first unread message

Akhil Anil

unread,
Feb 10, 2014, 12:45:24 AM2/10/14
to google-we...@googlegroups.com
I've developed a gwt application using MVP pattern ( View, Presenter). I need to add validation to my application but some stackoverflow links says that gwt mvp cannot have validations framework. I'm totally blown out.. i mean there has to be some way. Could someone please show me some tutorials or examples on how I can implement validations in a gwt applicaitons with mvp pattern. 

Thanks in advance...



-- 

Thanks and regards....

May God Bless us!

AkH!L.

Jens

unread,
Feb 10, 2014, 4:17:04 AM2/10/14
to google-we...@googlegroups.com
GWT supports/emulates JSR 303 (Bean Validation) on the client: http://www.gwtproject.org/doc/latest/DevGuideValidation.html

-- J.

RyanZA

unread,
Feb 10, 2014, 8:13:59 AM2/10/14
to google-we...@googlegroups.com
Slightly off topic, but do you know if the hibernate-validation support will be upgraded to version hibernate validator 5?

hibernate-validator-4.1.0.Final.jar requires on an old slf4j, and it plays a bit of havoc when including it in projects that require modern sl4j.

Jens

unread,
Feb 10, 2014, 8:51:55 AM2/10/14
to google-we...@googlegroups.com
Slightly off topic, but do you know if the hibernate-validation support will be upgraded to version hibernate validator 5?

hibernate-validator-4.1.0.Final.jar requires on an old slf4j, and it plays a bit of havoc when including it in projects that require modern sl4j.

I don't think anyone is working on it, see: https://code.google.com/p/google-web-toolkit/issues/detail?id=7661 .

However you can solve your issue by creating separate projects for client and server side which is kind of a good practice anyways. That way server libs do not interference with client libs.

-- J.

Ryan Chazen

unread,
Feb 10, 2014, 9:03:32 AM2/10/14
to google-we...@googlegroups.com
Yeah I have it working like that already, but it's still unfortunate. Maybe the best long term bet is to not use JSR 303 at all? It adds a bit more boilerplate code though.



--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/Vl0AFw486Tw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Thomas Broyer

unread,
Feb 10, 2014, 10:00:31 AM2/10/14
to google-we...@googlegroups.com


On Monday, February 10, 2014 3:03:32 PM UTC+1, RyanZA wrote:
Yeah I have it working like that already, but it's still unfortunate. Maybe the best long term bet is to not use JSR 303 at all? It adds a bit more boilerplate code though.

No one maintains JSR 303 emulation; so if you're not ready to contribute to it, not using it might be safer (I'd prefer you use and contribute to it though :) ) 
Reply all
Reply to author
Forward
0 new messages