Can you summarize the implementation differences?
On Tue, Apr 17, 2012 at 11:08 AM, Chris Ruffalo chris.ruff...@gmail.com wrote:
We've been over this before, I think, and several problems have gotten in
the way. It's not that we don't want to cooperate, we do, but I think that
it's too
Absolutely,
1) The gwt-validation project does not rely on the user doing anything in
order to mark classes as validatable or validators/constraints as usable.
No factories or etc. It instead uses a library to scan for constrained
classes.
2) Freemarker is used for creating templates of
We've been over this before, I think, and several problems have gotten in
the way. It's not that we don't want to cooperate, we do, but I think that
it's too divergent from the way that GWT works and wants things to work.
I also know it doesn't really conform to GWT's code style.
The goal,
There is another project that seems to be more advanced than current
status: http://code.google.com/p/gwt-validation/ ¿Is there a chance to
include it's work?
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Hi,
what is the current status/future plans of GWT's bean validation (JSR303)?
Looking at the issue tracker (issues labeled jsr303) it seems like that its
half way done but most of the still opened issues are 6-12 month old. Are
these issues real big blockers and will take their time to fix or
I believe we are getting an intern to finish this soon.
-Ray
On Mon, Apr 2, 2012 at 6:55 AM, Jens jens.nehlme...@gmail.com wrote:
Hi,
what is the current status/future plans of GWT's bean validation (JSR303)?
Looking at the issue tracker (issues labeled jsr303) it seems like that its
half
