requestfactory-*.jar libs in GWT 2.4

[Alexander Orlov]

I've build GWT 2.4... There are several requestfactory-*.jars in the
lib folder. Are those libs going to replace/consolidate any other GWT
libs in the coming release?

Currently I've to use hibernate-validator to be able to use RF
functionality. Are any of the rf-*.jars going to replace the hibernate-
validator lib? Actually I'm not using any hibernate functionality at
all; I'm using JPA2. However currently I've to provide the hibernate-
validator at runtime to satisfy RF's needs.

-Alex

[David Chandler]

Hi Alex,

The requestfactory jars in 2.4 are much smaller than gwt-servlet and are provided for the convenience of those using only RF for server communication. Validation will not be bundled with RF jars. You must continue to obtain validation from gwt-servlet-deps and/or validation-api + hibernate-validator jars.

/dmc

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
David Chandler
Developer Programs Engineer, GWT+GAE
w: http://code.google.com/

b: http://turbomanage.wordpress.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools

[Thomas Broyer]

Actually, hibernate-validator (or any other JSR303 validator) is not required. If you don't have a JSR 303 validator in classpath, you'll have an info message printed to your log at startup and that's all, it'll work OK (my unit tests are green despite the absence of hibernate-validator FWIW).

And you can easily turn the warning off if it bothers you, as it's using java.util.logging.

[David Chandler]

Minor clarification: a validation impl like hibernate-validator is not required except for some configurations of Spring, in which case the presence of validation-api without a corresponding impl will cause server startup to fail. IIRC, that's why we had to unbundle validation-api from gwt-servlet.

On Wed, Jul 13, 2011 at 11:15 AM, Thomas Broyer <t.br...@gmail.com> wrote:

Actually, hibernate-validator (or any other JSR303 validator) is not required. If you don't have a JSR 303 validator in classpath, you'll have an info message printed to your log at startup and that's all, it'll work OK (my unit tests are green despite the absence of hibernate-validator FWIW).

And you can easily turn the warning off if it bothers you, as it's using java.util.logging.

--

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/qwYENAR0qjgJ.

To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Thomas Broyer]

On Wednesday, July 13, 2011 5:28:34 PM UTC+2, David Chandler (Google) wrote:

Minor clarification: a validation impl like hibernate-validator is not required except for some configurations of Spring, in which case the presence of validation-api without a corresponding impl will cause server startup to fail.

OK, so Spring is worse that I'd imagined ;-)

 

IIRC, that's why we had to unbundle validation-api from gwt-servlet.

Oh, I thought it was because of Maven, and overall dependency management (where you'd then have, for instance, to exclude the validation-api dependency from hibernate-validator because the lcasses are already in gwt-servlet or live with potential conflicts if validation-api is updated to 1.1 or 2.0 but the 1.0 version bundled in gwt-servlet would be used because it comes first in the classpath –i.e. gwt-servlet defeating version conflict resolution of Maven, and possibility leading to breakages of third-party libs that depend on a newer version).

[David Chandler]

Yes, it was definitely about Maven. Folks using Maven with Spring were unlucky enough to spot the problem first.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/uF0MENLpcRoJ.

To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Alexander Orlov]

On Jul 13, 5:04 pm, David Chandler <drfibona...@google.com> wrote:
> The requestfactory jars in 2.4 are much smaller than gwt-servlet and are
> provided for the convenience of those using only RF for server
> communication. Validation will not be bundled with RF jars. You must
> continue to obtain validation from gwt-servlet-deps and/or validation-api +
> hibernate-validator jars.

Thx for this info!

Finally I've replaced the gwt-servlet 5MB monster with rf-server
(-4,5MB in runtime scope!) and assigned the provided scope to gwt-
servlet-deps.

-Alex

[Alexander Orlov]

On Jul 13, 5:41 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> On Wednesday, July 13, 2011 5:28:34 PM UTC+2, David Chandler (Google) wrote:
>
> > Minor clarification: a validation impl like hibernate-validator is not
> > required except for some configurations of Spring, in which case the
> > presence of validation-api without a corresponding impl will cause server
> > startup to fail.
>
> OK, so Spring is worse that I'd imagined ;-)

Don't use Spring either :)

Thx to your hint I could streamline my pom.xml: I've removed the
hibernate-validator; the "Unable to initialize a JSR 303 Bean
Validator" 'error message' actually doesn't matter at all. Since I
could remove hibernate-validator, I could also remove slf4j-log4j12
which was required by hibernate-validator. Also I've removed the
validation-api although its sources are still required at runtime(?).

-Alex