Problem with the Deferred Binding.

[Rodrigue Bouleau]

Dear all,

In our current project, we use the GWT Validation 1.0 and GWT 2.2. I
will try to upgrade to GWT-Validation 2.0 (latest trunk) and GWT 2.4.

I try to use the DevMode with the new libraries and I have one big
issue:

- Problem with the Deferred Binding.
When we try to validate a property on one bean, the
ReflectorFactory.INSTANCE (in the CoreValidatorImpl file, line 109) is
the ReflectorFactory (from the folder com\em\validation\emul\com\em
\validation\client\reflector) and not the "Runtime" ReflectorFactory
(from the folder com\em\validation\client\reflector).
I try to find a solution to use properly the RuntimeReflectorFactory
when we use the DevMode but GWT uses the directive generate-with.

To be sure that I do not miss something during the upgrade, I try to
launch the GWT-Validation Sample and I have this issue (in DevMode):

[ERROR] [gwt_validation_sample] Unable to load module entry point
class com.em.validation.sample.client.Gwt_validation_sample (see
associated exception for details)
com.google.gwt.core.client.JavaScriptException: (TypeError): 'console'
is undefined
at
com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:
248)
at
com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:
136)
at
com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:
561)
at
com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid(ModuleSpace.java:
289)
at
com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.java:
107)
at
com.em.validation.client.reflector.AbstractCompiledReflectorFactory.showKeys(AbstractCompiledReflectorFactory.java)
at
com.em.validation.client.reflector.AbstractCompiledReflectorFactory.getReflector(AbstractCompiledReflectorFactory.java:
45)
at
com.em.validation.client.reflector.ReflectorFactory.getReflector(ReflectorFactory.java:
38)
at
com.em.validation.client.metadata.factory.DescriptorFactory.getBeanDescriptor(DescriptorFactory.java:
94)
at
com.em.validation.client.CoreValidatorImpl.getConstraintsForClass(CoreValidatorImpl.java:
300)
at
com.em.validation.client.ValidatorImpl.getConstraintsForClass(ValidatorImpl.java:
72)
at
com.em.validation.sample.client.ui.MainUi.layoutTree(MainUi.java:75)
at com.em.validation.sample.client.ui.MainUi.<init>(MainUi.java:
66)
at
com.em.validation.sample.client.Gwt_validation_sample.onModuleLoad(Gwt_validation_sample.java:
43)

I think it is the same problem described above.

Does anyone have the same problem ?

Environment:
* Windows
* Eclipse 3.6
* Latest GPE Version
* OS Language: French

Regards,
Rodrigue

[chris.r]

Did you use the launch configuration included in the gwt-sample/launch
folder?

On Jan 9, 9:29 am, Rodrigue Bouleau <rodrigue.boul...@gmail.com>
wrote:

[Rodrigue Bouleau]

Yes.

The only difference between the SVN repo and my working copy is the
path to the exploded-war.

[chris.r]

The only thing I can think of is that you're using a different OS
language.

On Jan 10, 10:21 am, Rodrigue Bouleau <rodrigue.boul...@gmail.com>

[Frederic Conrotte]

Hello

I've got the same issue on my machine.

> The only thing I can think of is that you're using a different OS language.

You mean a different OS (Windows instead of Linux) or a different
language (French instead of English) ?

Thanks

Frederic

[chris.r]

Frederic and Rodrigue

Sorry this has taken so long to get back to you.  A lot of work has been done over the last several months?

Try the 2.1 snapshot and see if you have different results.

Thank you!

Chris

[chris.r]

In particular, the gwt-validation-sample now has a fully maven enabled run/test configuration.