Yes, I worked on a sample code that achieved that a couple of month
ago... I will try to post some sample code as soon as possible (first
let me find it);
for now, allow me to give you some impressions :
* the idea is nice (modularization, clear code, simple classes, etc)
* BUT the implementation is painful:
- I remember that I had to extend the EngineRemoteServlet
(supplied with Gilead) - not very cool
- it boasts that "no web.xml anymore" - forget it, you have to map
quite a bit before making it work
- at that time there was no "hello, world" example of setting it
up
- A LOT OF BOILER PLATE CODE (Action, Result for every possible
interaction with the server). Way too much to actually make something
useful. After you write about 5 Action + 5 Result classes, you will
get what I mean
- You lose the feeling of coding with Java, because your remove
service interface has only one method (doExecuteAction-and-
getAResult).
- You cannot have more methods on the same interface - aka service
- (again, Java feeling is completely lost)
- Because of generics restriction (even through Rpc interface is
using generics, the type erasure is not considered when extending an
interface, so you cannot do something like "interface UserService
extends Service<GetUserLoginAction,GetUserLoginResult>, Service<...>,
Service<...>
I will post some working code soon or you can PM me and I'll send you
the whole project
On Nov 23, 1:24 pm, Marcos Alcantara <marc...@gmail.com> wrote:
> Hi,
>
> Have anyone been successful on using these three altogether?
>
> Can someone please post some examples about how to configure them?
>
> Thanks!!!
>
> Marcalc
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=.
