Open GoogleCodeExporter opened 9 years ago
Hi,
Thank you for the patch.
Actually IsSerializable shouldn't be required with newer versions of GWT. This
error came up in the past when the application wasn't clean re-compiled with
GWT 2.x. This was for example already mentioned in Issue11. Could you please
try if the issue can be solved with hints of Issue11
(https://code.google.com/p/gwteventservice/issues/detail?id=11&can=1&q=IsSeriali
zable)? That would help a lot, because we would like to avoid adding
GWT-specfic classes/interfaces to the generic interfaces.
Thank you in advance.
Original comment by sven.strohschein@googlemail.com
on 23 Jul 2012 at 8:41
Comments from Hugues C.:
I have this error with a clean build of the application using GWT 2.3. I will
try to fix it by adding @GwtCompatible(serializable = true) from the guava
library. Would it be an acceptable fix?
The serialization error happens when the server is restarted while a client
using GWT Event Service is using the application (it does not happen
everytime). For now, I fixed the problem by providing a custom field serializer
for RemoteEventServiceConfigurationTransferable.
Original comment by sven.strohschein@googlemail.com
on 7 Aug 2012 at 7:40
Hi
I also saw this problem using 1.2.0 with GWT 2.3 but only when our customer was
running through a proxy. I added the patch and the problem appears to have been
resolved.
Regards
Neil
Original comment by n...@hydeabbey.net
on 7 Aug 2012 at 7:59
Hi Neil,
I could imagine that the proxy had cached some old GWT/JS resources. This could
for example happen when GWTEventService or the GWT version was updated and the
application wasn't rebuild completely or when some outdated resources were
still cached. Could that be the reason? Was also a previous version of
GWTEventService or GWT used and accessed via the proxy?
Regards,
Sven
Original comment by sven.strohschein@googlemail.com
on 3 Oct 2012 at 8:47
Hi Sven
This was a brand new customer install with a clean production build that has
only ever run gwt 2.3.0 with gwteventservice 1.2.0, so I don't believe it could
have been contaminated with old cached data.
Neil
Original comment by n...@hydeabbey.net
on 3 Oct 2012 at 9:45
Original issue reported on code.google.com by
m.j...@griffith.edu.au
on 23 May 2012 at 12:39Attachments: