Re: EventBus in 2.4
I've filed an issue. http://code.google.com/p/google-web-toolkit/issues/detail?id=6653 Should be an easy fix - just changing the import in Activity would do it I imagine. -- 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/-/sbOLnnCLtAUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: EventBus in 2.4
I have been looking forward to 2.4 for the built-in validation support. However, those classes still have comments with don't use this in production caveats. Maybe the RC1 tag is premature then and there's going to be more work done. Or maybe 2.4.0 will just introduce the validation framework in an experimental preview. Any insight from anyone that's the project would be appreciated. -- 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/-/ltlTst1mB8kJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
EventBus in 2.4
I was looking at 2.4.0 RC1 and noticed that I had some deprecation warnings with regard to EventBus. Specifically, PlaceController has deprecated methods using com.google.gwt.event.shared.EventBus, favoring instead com.google.web.bindery.event.shared.EventBus. However, I have noticed that Activity still uses the old location exclusively. Since both of these are part of the places support, it seems like that framework is currently inconsistent. Is this a situation that will continue through the actual release? If so, is there a recommended approach as to which one to use in a given situation? I'm guessing we'd just be stuck with the warnings in 2.4. Thanks. -- 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/-/B4jD89VgZIsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: EventBus in 2.4
This mess has started with 2.3. If I simply upgrade my project from 2.2 to 2.3 without migrating from gwt to web.bindery, the project compiles but fails at run-time failing to locate a proxy when receiving a response from the server. But upgrading 2.2 to 2.3 with migration from gwt to web.bindery fails to compile. I'm completely ignoring 2.3 for now and may be ignore 2.4 until all the dust settles down. -- 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/-/kRIup0cxB7sJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: EventBus in 2.4
Just tried to migrate from 2.2 to 2.4 RC1.
First, the project didn't compile because of internal compiler errors. All
obsoleted RF-related stuff is removed (good), but there is no way to migrate
to 2.4 as it was possible to 2.3 (for some people) if the project uses RF.
After migrating from gwt to web.bindery the internal compiler error
disappeared (good).
After fixing some incompatibilities the project now compiles and the
application starts. (good)
But it fails to run in exactly the same spot as when moving from 2.2 to 2.3
migration
from gwt to web.bindery (bad). And in 2.2 the application runs fine.
Here is the culprit:
interface P extends EntityProxy { ... }
interface PA extends P { ... }
interface PB extends P { ... }
interface R extends RequestContext {
RequestLong queryCountOfP(P p);
}
When queryCountOfP() accepts an instance of PA, the callback is called fine.
When queryCountOfP() accepts an instance of PB, the failure occurs:
java.lang.IllegalArgumentException: Unknown proxy type PB
The server receives the call, the argument type of the service method is
correct (B), but after returning to the client the following method throws
an exception:
at
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext.createProxy(AbstractRequestContext.java:489)
Why does the method fails on PB but not on PA? Is there anything wrong with
this usage pattern?
Thanks!
--
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/-/dteQgwksMQEJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
