Hi Ganesh,
Although I'm not totally sure of your GWT integration goals, I imagine they
involve a smoother user experience by Ajax-ifying your application.
If that's the case, my advice would be to take steps to eventually end up in
situation 2) described above. Depending on how your business logic flows
through your server-side, you could potentially implement RPC services that
would replace existing action servlets and over time, redefine your
server-side architecture in terms of GWT RPC services.
This might seem like an all or nothing approach, but it will lead to a net
win in terms of application performance. If you're not looking to totally
redefine your application and just add Ajax bits to it using GWT, that can
be done too. Let me know if you want to consider doing that and I would be
happy to provide more info (or a quick search for "RootPanel.get("id").add"
on the group should turn up some useful results).
As you mentioned, using solution 2) will effectively break and require
replacing your existing Struts-style architecture. However, I don't think
that will affect the scalability of your application in terms of server
load. In fact, it should make your application even more scalable since
extra roundtrips would be avoided. Unless you meant scalability of your code
base for maintenance purposes, in which case I still don't think it will
lead to scalability problems.
Hope that helps,
-Sumit Chandel
On Sun, Apr 26, 2009 at 11:41 PM, newtoGWT <[email protected]> wrote:
>
> In the existing webapplication,
>
> my action class receives the request, validates it, hits the DAO,
> builds the Value Object (nothing but a bean class), and finally
> returns the VO to the action class. This value object is then set into
> session and retrieved in JSP page. (Normal request and response model)
>
> To implement GWT in the existing webapp,
> 1. Using HTTP request to call my action class, convert the value
> object in JSON and write it in to response. Access the json in GWT
> class and paint the page.
> Advantages: i am not breaking my existing architecture, going
> through action class.
> Disadvantages: Extra round trip to convert value object to json and
> vice versa.
>
> 2. Using RPC to call service method directly and get the value object
> from service directly.
> Advantages: I can get my value object with out any extra round
> trip.
> Disadvantages: Breaking my existing architecture, by calling
> service directly (coz scalability might be an issue later, just a
> futuristic thought not sure though).
>
> Above 2 approaches has their own adv. & disadv. please guide to choose
> the best solution/approach to follow so that GWT can be integrated
> successfully without issues.
>
> Thanks,
> Ganesh R
>
> Disclaimer:
> i am a beginner in GWT! so question can be silly some times :)
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
