Skip to content
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

Android Library to GWT 2.5.1 Compatible #31

Closed
GoogleCodeExporter opened this issue Mar 21, 2015 · 7 comments
Closed

Android Library to GWT 2.5.1 Compatible #31

GoogleCodeExporter opened this issue Mar 21, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

Cross-posted here: 
http://stackoverflow.com/questions/19050147/gwt-and-android-communication-serial
ization-issue

The interesting thing is, that it works on the desktop with the desktop jar, 
but it does not work on Android...

What steps will reproduce the problem?
See this: 
http://stackoverflow.com/questions/19050147/gwt-and-android-communication-serial
ization-issue

What is the expected output? What do you see instead?
Getting the result from the server. "Invalid type signature"

What version of the product are you using? On what operating system?
0.4 Android

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 27 Sep 2013 at 12:36

@GoogleCodeExporter
Copy link
Author

Sorry for the delay. I am unable to verify your issue as described (using your 
provided src, it works in my dev environment using an JB emulator), though I 
had seen your specified error during development of the Android library. I have 
found that many of the "Serialization" issues in GWT are usually something 
small such as unserializable member types, missing interfaces, default 
constructors, etc. Since it seems you have already addressed those 
possibilities, please verify the following: 

Version of GWT being used in web-app on your machine. Android OS Version being 
tested on (emulator or Device) and which device if appropriate.

Though I dont expect it to be an issue, the Android library is compiled with 
GWT 2.5.0 src, so it's possible (an as yet untested theory) that if the server 
is running GWT other than 2.5.0, the RPC serialization is failing due to that. 

This would also explain why the desktop client works and the android library 
does not. The desktop client syncproxy library is compiled against GWT, not 
with GWT, so you link your version of GWT at compile time. The Android library 
was compiled directly with GWT src code for 2.5.0 with a few custom overrides 
in order to reduce the size of the library to be usable and manageable in the 
Dalvik environment.

Original comment by [email protected] on 6 Oct 2013 at 10:03

@GoogleCodeExporter
Copy link
Author

Brilliant, switching the Example app to GWT 2.5.0 did the trick. Can you give 
me an estimate as to when you would be able to update the library to 2.5.1? If 
you don't have the time to do it, I could switch the main app to 2.5.0. 
However, I'd prefer staying with the latest release if possible. Please let me 
know if you're planning to update to 2.5.1! :)

Original comment by [email protected] on 7 Oct 2013 at 9:00

@GoogleCodeExporter
Copy link
Author

I'll take a look at the 2.5.1 source this week and see if I can pull it off. If 
so, I'll try to get a 2.5.1 compatible library out within a week or 2. If major 
changes occurred to the files, it will likely take me longer to filter things 
out to get it to be compatible with 2.5.1 (based on my schedule, upwards of a 
month). If it looks like it will take that long, I may end up just holding off 
until the 2.6 release (expected early Dec). Keep an eye on the wiki's and issue 
tracker for the project. I'll update this issue in relation to when/whether 
I'll be able to get a 2.5.1 library up and available

Original comment by [email protected] on 7 Oct 2013 at 9:00

  • Changed title: Android Library to GWT 2.5.1 Compatible
  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

It appears that the changes in 2.5.1 were relatively compatible with the 
library changes i made, so I've got an update of the library that is passingthe 
automated tests in the same manner as the previous version, but I'd like you to 
test it in your dev environment before I put it on the download's list. Please 
send me an e-mail when you can and I'll e-mail you the updated library for 
trial. Enum's have been failing the automated tests due to a configuration 
issue with the GWT source code for enum tests, so my automated testing couldn't 
verify that this change reflects/resolves the issue you were experiencing. I 
will put together a manual test to verify your issue and see if this resolves 
it, but a faster check would be to see if the new library still gives you the 
issue. Thanks

Original comment by [email protected] on 22 Oct 2013 at 7:13

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Not sure if this is the right issue to comment on, but I found that replacing 
the regex in RPCPolicyFinder from \'([A-Z0-9]){32}\' to 
[\'\"]([A-Z0-9]){32}[\'\"] works better with GWT 2.5.1 (with appropriate quote 
replacements further in the code)

Original comment by [email protected] on 24 Oct 2013 at 9:05

@GoogleCodeExporter
Copy link
Author

Can you verify what you mean when you say it works better? Where you running 
into instances with the Policy Finder in 2.5.1 where it was not being found 
without that regex modification or something else?

Original comment by [email protected] on 28 Oct 2013 at 6:19

@GoogleCodeExporter
Copy link
Author

This issue is considered complete with no further feedback available regarding 
the RPC Policy Finder

Original comment by [email protected] on 26 Feb 2014 at 7:12

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant