Les,
Your methodology ends up using the same basic idea as what I'm
currently using: annotations. The problem is that I end up having a
class on the client for every procedure on the server. Maybe I could
consolidate them into one big class with a bunch of tiny inner
classes.
In any case, it
Nathan,
You might want to have a look at super-source, if it's still called
that. If you are willing to put empty definitions of your server-side
classes on the client, then you could reference the class names from
client code without having to modify GWT. It's been too long since
I've touched
On Wed, Jan 27, 2010 at 5:14 PM, Nathan Wells nwwe...@gmail.com wrote:
interface RpcService {
call(Class? procedureClassLiteral, AsyncCallback callback,
Arguments args)
}
Makes sense.
Have you considered, though, the security implications of client code
sending an arbitrary class
Thanks Ian!
Nathan Wells
On Thu, Jan 28, 2010 at 9:33 AM, Ian Petersen ispet...@gmail.com wrote:
Nathan,
You might want to have a look at super-source, if it's still called
that. If you are willing to put empty definitions of your server-side
classes on the client, then you could
Can someone point me to a place in the GWT code where I might be able
to produce a patch or something? I realize it's probably not the
GWTers highest priority, but I could use some guidance.
Unless of course the silence is an indication that what I'm proposing
is against the spirit of GWT. I
On Wed, Jan 27, 2010 at 3:57 PM, Nathan Wells nwwe...@gmail.com wrote:
Can someone point me to a place in the GWT code where I might be able
to produce a patch or something? I realize it's probably not the
GWTers highest priority, but I could use some guidance.
I don't know how you would do
Let me back up a little bit. There may be a way to do what I want
without changing GWT's core. All I want is to be able to change the
following interface:
interface RpcService {
call(String procedureClassName, AsyncCallback callback, Arguments
args)
}
into something similar to the
Think about an Event based RPC mechanism as outlined in this Article..
http://sonymathew.blogspot.com/2010/01/gwt-jee-blueprint.html
Essentially, RPC is then merely firing/listening to events. You
merely extend RemtoteRequestEvent and RemtoteRequestEvent and make
sure any member content you add
Sony,
I disagree with taking an event-based approach to RPC, but this isn't
really the forum for that discussion
John,
My problem is not Class serializability, but rather the fact that the
GWT compiler rejects any code path that has
SomeServerProcedure.class, since the compiler thinks it will
