Hi Arul,
GWT RPC is anynchronous therefore you must follow the steps outlined
to use GWT RPC. If your client wishes to upgrade from a Struts/JSP
style application to a GWT UI, then it is usually better to replace
the entire current server side UI mechanism (i.e. the action classes
and JSP's etc) with the new GWT client and make the GWT client talk to
the existing application server implementation (e.g. EJB's/Spring etc)
directly via GWT RPC servlets.
have a look at this explanation from Summiit:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/af54912ddc69a3fd#
It is possible to do it in "chunks" if they wish to test drive the
idea. You can pick a particular series of JSP's and replace one with a
GWT module hosting version that replaces them. You can then jump back
to the original struts application using RequestBuilder to mimic a
struts *.do call. If you cannot do the whole UI in one iteration, this
would probably be your best approach.
It is possible to embed GWT code within an existing JSP, but this has
more limited use because each GWT module runs within one page (i.e.
JSP) therefore you would need one GWT mini-app per JSP you wanted to
enhance none of which can easily talk to each other.
regards
gregor
On Dec 9, 9:02 am, Arul <
arulmanikandan.sriniva...@gmail.com> wrote:
> Hi Gregor,
> I would like to thank you for your reply.
> I understood your answers regarding changing of presentation layer
> concepts. But my client asked me to replace only presentation (Web
> Tier) and I suggested GWT. I wanted to confirm the possibility of
> doing it. I am doing research on that.
>
> In order to code GWT RPC , I followed the steps mentioned athttp://
code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=goog...,