Found in GWT Release: All

Detailed description: We need to look into removing the IsSerializable interface as a criteria using RemoteServices. Having this interface makes interoperability with existing POJOs impossible.

It is better to roll this up into the next revision of GWT RPC; which should take place post 1.4.

I'm going to get shot for this.

Workaround if you have one: None

Links to the relevant GWT Developer Forum posts:

Shot? People have been requesting this for some time. Let me be the first to say, +1.

Thanks b

Related to http://code.google.com/p/google-web-toolkit/issues/detail?id=21

Hi,

I've come up with an easy workaround to make serialization work for my project without polluting DTO's with marker interfaces.

All you need to do is put the attached file under com/google/gwt/emul/java/io in gwt-user.jar.

This will make GWT compiler think that every classes marked with java.io.Serializable are serializable.

Cheers,

Tamas

The combination of the addition of java.io.Serializable to emulated classes [http://code.google.com/p/google-web-toolkit/issues/detail?id=21&can=2#c19] and the fact that Serializable is now equivalent to IsSerializable [http://code.google.com/p/google-web-toolkit/issues/detail?id=933&can=2#c2] means that cserveny.tamas' proposed workaround is totally redundant. While I can't see a reason why it wouldn't work for any prior releases, GWT 1.4RC and later have solved this problem already.

-Joshua Yanchar

Hi,

will you remove the IsSerialization interface for the release 1.5 ? now we have to define if we have to develop to wrap our dto from EJB to GWT, implementing IsSerializable... but if you remove IsSerializable in the next Step then we'll wait for this one.

We have tried to migrate from 1.4.10 to 1.4.60 and as notice the issue 1605, the Serializable interface can't be used in the 1.4.60 version for dto.... it's a real problem for us because we can't stay officialy in a beta version .......

Thanks

Elvio

See the update to issue 1605. java.io.Serializable does work as long as the RemoteServiceServlet can find the serialization policy file.

I believe this has been dealt with.

Keeping IsSerializable as a GWT only serialization marker for those that desire GWT serializable classes, but don't want to implement java.io.Serializable, which marks a class for both GWT and Java serialization.

IOW, no immediate plans to remove IsSerializable.