Nathan:
The docs say:
"The type has at least one serializable subclass."
I think that is my case - the type is an interface and it does have
serializable subclasses, and only serializable subclasses.
Paul:
I've tried to replicate the problem in a dummy project, but was not
able to. The project w
Nathan Wells wrote:
> I don't think so, as I believe that is how it's supposed to work.
You're not supposed to have to put things in the same package to make
serialization work.
Can the OP put together a simple example that shows the error and post
all the code? It could be that things that were
I don't think so, as I believe that is how it's supposed to work. From
the docs (http://code.google.com/webtoolkit/doc/1.6/
DevGuideServerCommunication.html#DevGuideSerializableTypes):
A type is serializable and can be used in a service interface if one
of the following is true:
The type is primi
Yeah I've left that out in the example, it of course is marked with
IsSerializable.
However! - I've found a solution (just needed to recall that I've had
similar problem with Interfaces+Classes already):
A Class (or Enum) type extending the said "non-serializable" interface
(MyIface in the above
Don't you also need to do:
class POJO extends Serializable ?
I got many alerts about this in my classes.
On Tue, Jul 21, 2009 at 3:51 PM, Juraj Vitko wrote:
>
> I'm trying to RPC-send an interface member in a POJO - all types
> implementing this interface are Enums (see the example below pleas
changing the POJO.iface field to:
Enum iface;
doesn't help either.
On Jul 21, 8:51 pm, Juraj Vitko wrote:
> I'm trying to RPC-send an interface member in a POJO - all types
> implementing this interface are Enums (see the example below please).
>
> Now, the application works 100% in both host
