Home/ Questions/Q 4607678
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T00:44:13+00:00

We have an existing app which is mostly JSP based for front end and

  • 0

We have an existing app which is mostly JSP based for front end and Java/DAO based back end connecting to an oracle DB. This is an enterprise level trading application.

Recently our management gave directive to use GWT to have a more modern look and feel to our front end pages. So we have migrated a few existing pages to GWT as well as all brand new development is in GWT. GWT is being used for both rendering front end as well as server side communications and AJAX.

However, I am concerned about fully embracing GWT as it is a client side architecture where most of the rendering logic processing happens on the client side.

  1. Is my concern justified?

  2. What other architectures would you recommend? Spring MVC/Webflow? Something else?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’d start with a service architecture. Keep the processing in the back so you can swap UIs in and out without rewriting the back end.

    They can be SOAP or REST. You need not make them heavy.

    Best to not depend on JSP or GWT for the processing. Ever hope to make this available on iPad? It’d be good to be able to do it without rewriting the whole thing.

    Start with coarse-grained services that match your use cases.

    • 0