*I've updated the issue (
http://code.google.com/p/google-web-toolkit/issues/detail?id=4438) with a
workaround, let me know if it doesn't work for anyone. *
*
*
*- Chris
*
On Wed, Jan 6, 2010 at 1:42 PM, Chris Ramsdale cramsd...@google.com wrote:
Please star the issue and add any relevant data
I'm experiencing the same problem.
On Dec 8 2009, 6:24 pm, Luis Fernando Planella Gonzalez
lfpg@gmail.com wrote:
Hi.
We're using GWT 1.7 and I'm starting to experiment with 2.0 RC2 to
evaluate GWT.runAsync().
However, now as I compile the app, I get warning for deprecations in
all RPC
Please star the issue and add any relevant data you may have.
- Chris
On Wed, Jan 6, 2010 at 8:14 AM, Bert roexb...@gmail.com wrote:
I'm experiencing the same problem.
On Dec 8 2009, 6:24 pm, Luis Fernando Planella Gonzalez
lfpg@gmail.com wrote:
Hi.
We're using GWT 1.7 and I'm
Could you add a bug to the GWT issue
trackerhttp://code.google.com/p/google-web-toolkit/issues/list
?
Done: http://code.google.com/p/google-web-toolkit/issues/detail?id=4438
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this
This is a bug. The ListListObject return type is causing the compiler to
generate serialization code for any class X that extends ListT, where T is
an interface that has a implementing class that extends class X. The
following code will reproduce the issue:
@Deprecated
public class MyTest extends
I'm seeing the problem as well. But interestingly I didn't see the
generated warnings until I stored the List object into a variable on
the client. So the RPC call itself is not where the issue is for me.
I was returning lists from the server and only using the contents by
calling the toArray()
Bah. Writing in haste I worded it so badly.
until I stored the List object into a variable on the client.
I should have said: until in my client code I assigned the object of
type List to a variable declared as type List.
and stored the resultant ListFoo object into a variable on the client
The same problem.
We're facing this after upgrading to gwt 2.0.
Any ideas?
Thanks in advance!
On 8 дек, 19:24, Luis Fernando Planella Gonzalez lfpg@gmail.com
wrote:
Hi.
We're using GWT 1.7 and I'm starting to experiment with 2.0 RC2 to
evaluate GWT.runAsync().
However, now as I
This issue is still present on GWT 2.0 final.
I've made some tests: creating a new GWT project with Collections in
RPC methods don't result in such code being inserted in the generated
JavaScript.
The point is: our project is quite huge, but I can confirm that there
are no occurrences of any of
Hi I'm having the same kind of problem.
in my app i use some libraries/object written in Java 1.4 style
the objects implement Serializable but contain Lists or Maps which are
declare without parameters
i mean List instead of ListE, as the Java 1.4 requires
and some RPC classes return this kind of
Just found the answer, and luckily in my case it was simple to
solve
I have a subtype of ListT called PageImplT, which had another
ListT containing the page items, plus the total count.
Then (and I think is a problem in GWT compiler), the compiler resolves
FocusListenerCollection, which
In fact, there is a very easy way to reproduce it:
Just create a RPC method which returns ListListString. You'll see
references for those deprecated collections.
On 11 dez, 17:39, Luis Fernando Planella Gonzalez lfpg@gmail.com
wrote:
Just found the answer, and luckily in my case it was
Hi.
We're using GWT 1.7 and I'm starting to experiment with 2.0 RC2 to
evaluate GWT.runAsync().
However, now as I compile the app, I get warning for deprecations in
all RPC methods which return collections. I guess it's because the
result is declared as java.util.Collection, and the deprecated
13 matches
Mail list logo
