Chris,
Sorry, I was unclear and also a bit wrong in my description above.
First, the class that gets generated is NOT TestMessageListenerImpl,
TestMessageListenerImpl is the class that the user of the framework
defines to be the "real" listener class in the client and is of less
importance.
I missed to mention the class AbstractRpcObserverWrapper. This is the
class that the generated class extends (I wrote AbstractRpcObserver,
which is wrong, but this doesn't really change the reasoning since
both implement Serializable). Apart from extending this class, the
generated class also implements TestMessageListener.
AbstractRpcObserverWrapper looks like (although the internals
shouldn't matter for the resoning):
public abstract class AbstractRpcObserverWrapper implements
RpcObserverWrapper, Serializable {
protected int observerId;
protected int rpcReversedSessionId;
@Override
public int getObserverId() {
return observerId;
}
@Override
public void setObserverId(int listenerId) {
this.observerId = listenerId;
}
@Override
public int getRpcReversedSessionId() {
return rpcReversedSessionId;
}
@Override
public void setRpcReversedSessionId(int rpcReversedSessionId) {
this.rpcReversedSessionId = rpcReversedSessionId;
}
protected boolean matches(String methodName, List<Class<?>>
parameterTypes, RpcObserverInvocation invokation) {
if (!methodName.equals(invokation.getMethodName())) {
return false;
}
List<JavaType> invokationParametersTypes =
invokation.getParametersTypes();
Iterator<JavaType> invokationParametersTypesIterator =
invokationParametersTypes.iterator();
for (Class<?> parameter : parameterTypes) {
if (!invokationParametersTypesIterator.hasNext()) {
return false;
}
JavaType invokationParameter =
invokationParametersTypesIterator.next();
if
(!parameter.equals(invokationParameter.getAsClass())) {
return false;
}
}
if (invokationParametersTypesIterator.hasNext()) {
// Different number of parameters.
return false;
}
return true;
}
}
When the user of the framework needs an instance of
TestMessageListenerImpl, he will do:
TestMessageListener testMessageListener = GWT.create
(TestMessageListenerImpl.class);
and be handed out an instance of the generated class.
Once I get back in the office I will supply the code for the generated
class and also for the gwt.rpc so you can see it.
/Martin
On 12 Jan, 21:27, Chris Ramsdale <[email protected]> wrote:
> My comments/questions inline:
>
> > The generated class extends this AbstractRpcObserver (and is thereby
> > Serializable) and implements the TestMessageListener interface. An
> > instance of the generated class is used as argument in the
> > addMessageListener method invoction in the RPC service.
>
> If I understand this correctly, your custom generator is generating
> the TestMessageListenerImpl
> class you reference above. Correct?
>
> > This is part of a framework for asynchronous invocations of observers
> > in the client from the server. The idea is to have the framework
> > generate the plumbing code so that any interface can be used as a
> > "listener" to be added to the server.
>
> > Everything works like a charm in GWT 1.7.1, but as you say, that could
> > be just a happy coincidence.
>
> Yes. Either happy coincidence, or the order in which we ran the generators
> was different in 1.7.1. Not necessarily my area of expertise, but I'm asking
> around back here.
>
> Would you mind emailing me your gwt.rpc file? I would like to see what
> classes have been whitelisted.
>
> /Martin
>
>
>
>
>
> > On 11 Jan, 23:03, Chris Ramsdale <[email protected]> wrote:
> > > Martin,
>
> > > The RPC serialization generator is most likely being run before your
> > custom
> > > generator. As a result serialization code, whitelisting, etc... are not
> > > being created. Unfortunately there is no way of guaranteeing that your
> > > generator is run before the RPC serialization generator.
>
> > > That said, I did have a couple of thought:
>
> > > 1. Within your RPCs, what class is your server expecting?
> > > 2. Rather than generate classes that you send across the wire, would it
> > be
> > > possible to send an interface, and generate client-side classes that
> > > understand how to instantiate themselves based on said interface?
>
> > > 2010/1/11 Martin Söderström <[email protected]>
>
> > > > Hi,
>
> > > > I have a custom Generator (subclassing
> > > > com.google.gwt.core.ext.Generator) class that generates a class to be
> > > > used as argument in an RPC method. The generated class implements
> > > > Serializable and the interface that the RPC method expects. This used
> > > > to work in GWT 1.7, but with GWT 2.0 I get a
> > > > com.google.gwt.user.client.rpc.SerializationException. Using
> > > > IsSerializable instead of Serializable does not make any difference.
>
> > > > It feels like, in GWT 2.0, the scanning for RPC serializable classes
> > > > does not take into consideration the custom generated classes. Does
> > > > anyone know anything about this? A possible workaround?
>
> > > > /Martin
>
> > > > --
> > > > 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]<google-web-toolkit%2Bunsubs
> > > > [email protected]><google-web-toolkit%2Bunsubs
> > [email protected]>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > --
> > 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]<google-web-toolkit%2Bunsubs
> > [email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-web-toolkit?hl=en.
--
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.
