-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GWT 2.7 super dev mode #194
Comments
If you apply #171, does it help? Try it and let me know...I'm swamped this week but will do my best to help. |
Yes, if i apply #171 there's no compilation error. |
Nomn in 2.4.0 by default |
This problem still exist in:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Guys,
I'm using Atmosphere GWT extension branch 2.2.2-GWT27 and i have a little problem when i use this code piece:
AutoBeanClientSerializer json_serializer = new AutoBeanClientSerializer();
json_serializer.registerBeanFactory(beanFactory, ITest.class);
Super dev mode compilation error is:
[ERROR] Errors in 'org/atmosphere/gwt20/client/AutoBeanClientSerializer.java'
[ERROR] Line 85: Only class literals may be used as arguments to GWT.create()
If i remove the problematic lines from my code, and i left only the package import of AutoBeanClientSerializer class, the gwt compiler still produce the same error. I've checked the jar file, and i've found that the jar file containing both source and class files. Is it possible that the gwt compiler trying to recompile java sources from dependent jar files?
My project - and this problematic code piece - has worked without any problem with gwt 2.6.1 and atmosphere GWT extension 2.2.0 using not super development mode.
I've found a similar issue in closed state, but i'm nearly sure my interfaces are valid.
#169
I've found a pull request with a possible fix by removing the problematic method from AutoBeanClientSerializer class.
#171
Sorry for my english, i'm not a native.
Could you help me pls?
Cheers
The text was updated successfully, but these errors were encountered: