Andreas,
Yes my RPC return types are concrete.
please see my project setup below
Proj-gwt (no dependencies)
Src
Com
Acme
AcmeModel.xml (gwt file saying to only use com/acme/client
as source for gwt, no entry point)
Client
AbstractFoo.java
Lets say I have a class
com.mycom.app.AbstractMessage
There is another class in
com.mycom.model.QueryResponse
QueryResponse extends AbstractMessage and notice they are in different
pacakges
com.mycom.model is a GWT Module and in the module XML
When I compile model there are errors. However
Lets say I have package : com.mycom.model
It has following classes
com.mycom.model.PlatformMessage (an interface)
com.mycom.model.AbstractMessage (an abstract class that implements
PlatformMessage)
com.mycom.model.QueryMessage (a concrete implementation of
AbstractMessage)
Now there is
Do you use that abstract base class as a RPC parameter? If so, *of
course*GWT has to look for and try to compile all sub classes and
implementations
*since* they might get used in a RPC and hence need to be serializable and
compilable.
To avoid this you can either:
- refactor your RPC to use only
