On Wednesday, June 15, 2016 at 10:49:56 AM UTC+2, Jens wrote: > > If it wouldn't be a feature RequestFactory depends on >
Oh, you're right, the Editor Framework depends on javax.validation.ConstraintViolation but doesn't implement it so one could probably have 1.1.0.Final in classpath without problem (assuming all interface dependencies are usable without super-source). The real issue here (besides JSR 303 emulation itself) is RequestFactory, which *implements* ConstraintViolation; but we could possibly add the 1.1.0.Final methods (without the @Override, to be compatible with 1.0.0.GA). For the longer term, use of ConstraintViolation in the Editor Framework and RequestFactory should be sunsetted, a new method taking EditorErrors (or some other custom type, e.g. SimpleViolation) added to EditorDriver, and RequestFactoryEditorDriver#setViolations and Receiver#onViolation de-deprecated, possibly with a public API to turn an RF Violation into an EditorError/SimpleViolation for those using a SimpleEditorDriver. > I think validation support would have been extracted already from GWT into > its own project and either let it die or let someone pick it up to maintain > it. > Absolutely! Given the above, we could actually do that already I believe. Probably won't be for 2.8.0 though (too late; sorry for not realizing this before); but I think we should at least officially deprecate JSR303 support in GWT 2.8 (this is long overdue actually): https://github.com/gwtproject/gwt/issues/9367 -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
