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 with the above problem results into a 900 kB
script, so it would be a longer process to isolate.

I'm 100% positive though, that in order to be able to declare a field
of an interface type, for the interface to be accepted, I have to
declare at least a single dummy type implementing that interface, and
this type must reside in the same package/directory as the interface.
Having other types implementing that interface, defined in other
packages than the interface, doesn't help.

The field then can be used by any other serializable type implementing
that interface, no matter what package.

The project this is occuring in (app-engine GWT app) consists of
multiple modules, both defined in source (my own GWT libs being built)
and also as a jar file (GXT).

I plan to upgrade to GWT 2.0 soon, and compile GWT from sources so
that I can be of more help solving things like this.
I currently use GWT 1.6.4.

J.


On Jul 23, 10:22 am, Paul Robinson <[email protected]> wrote:
> 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 missed out in the
> original post are important.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to