if you consider it well: > http://code.google.com/webtoolkit/tutorials/1.5/RPC.html will claims a special note : "Important: GWT RPC services are not the same as web services based on SOAP or REST. They are simply as a lightweight method for transferring data between your server and the GWT application on the client. To compare single and multi-tier deployment options for integrating GWT RPC services into your application, see the Developer's Guide, Architectural Perspectives."
if you´r not paying attention or respect to the different rules of communication, you can tell us later, how to involve a webservice from a gwt.client. my chain is: gwt (js-client) -> rpc(remoteservice(proxy)) -> interface(@remote)- >serviceclass(@statefull/@stateless) and the way back. > Being that that service is a servlet there's no reason why one shouldn't use > an access to a db, right, dont let a client directly on your db ;) > a call to a webservice or whatever not what ever, if your programming it with that behavior, then i is it no wonder, that your fish in the aquarium going to dive. > permitted by a servlet itself. therefore the beans are created, the servlet (to serve) is to satisfied the client, not as a "workerbean" > I'm doing a browser -> (gwt) servlet -> webservice. thats your choice > I don't care about the rpc communication between the browser and the server, what do you care for ? > the webservice can take much time to answer, and being the call asynchronous > it's all ok: when the method returns the > callback on javascript will be executed. take care with your deductive logic --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
