Wednesday, August 31, 2011

Re: GWT : How to call SERVLET FROM GWT_SERVLET and How to return value from target servlet to source servlet?

Modularize. You can have a service pojo object and invoque this in both servlets.

2011/8/31 vaibhav bhalke <bhalke.vaibhav@gmail.com>

I have 2 servlets.

One In GWT module i.e BasicServiceImpl extends RemoteServiceServlet implements BasicMassUpdateService

and other servlet TargetServlet extends HttpServlet in TargetServlet in diff module/package com.comp.server.servlets

I am using GWT-RPC in my gwt module. I want to write one method getRecordList() in BasicServiceImpl which returns list of record on client side.(right now I am sending dummy data in record list)

In other servlet i.e TargetServlet RecordList formed from database value.

Use case: When we call getRecordList() method using rpc then I want to call SERVLET : TargetServlet to get recordlist, TargetServlet will return recordlist to getRecordList of Gwt_servlet and finally getRecordList() returns recordlist on client side

1: How to call other servlet(TargetServlet) from GWT_SERVLET i.e BasicServiceImpl

2: How to send recordlist from TargetServlet to getRecordList() of BasicServiceImpl(GWT SERVLET)

Any help or guidance in this matter would be appreciated



--
Best Regards,
Vaibhav





--
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
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 google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment