Re: Support for both Web and Desktop front-ends [Architecture]
On 7/14/2011 6:02 AM, Arved Sandstrom wrote:
On 11-07-13 11:05 PM, Warren Tang wrote:
Thanks Arved for your detailed explanation. It really make things much clearer for me.
As I don't want to learn so much new things at a time, I should keep it as simple as possible. If Java SE can get the job done, I won't go for Java EE or Spring this time.
My current understanding is that I can really do it with Java SE only. That is GWT for the web and Swing for the desktop, with no Spring or Java EE involved. If I can properly divide the code into the 4-tiers as you described, I believe I can get pretty good results.
For me it's like the ".NET" way which I am familiar with. As my knowledge on Java grows, I may go for other possibilities.
Regardless of one's personal feelings about Spring, it's a non-essential
framework. You don't _need_ it, no.
I'm not a GWT expert, but even a GWT app that produces HTML and
Javascript is still a web app that needs a web server, so by definition
it's Java EE territory. For example, even a basic GWT application will
be packaged according to Servlet API guidelines.
GWT is traditionally compared with Java EE we frameworks.
And if it is using the GWT server side stuff then it has to be used
with a servlet container.
But it is actually possible to only use the client side stuff and have
Apache httpd or IIS serve up the generated HTML and JavaScript without
having any Java EE server in the production environment.
Arne