Win a copy of Event Streams in Action this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

What Level of Java Programmer Is GWT For?

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Is GWT for advanced users only? Or is familiarity with it something that ought to be mastered as soon as possible by all those learning Java?

Thanks,

Ben
 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, GWT for anyon just now Basic java. if you now C# is also good to start learning GWT
 
Ben Stanley
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Good to know! Unfortunately, I do not know C#
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
GWT does not require an advance level of java knowledge, but you do need to have some knowledge of java GUI development (unless you use the ui xml pattern which requires some knowledge of html). You should also have some idea of how web technologies and ajax works.
 
author
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi! When we hire people for GWT programming, if they do not already know it, we ask for Java+Swing knowledge. It's quite simple going from there to GWT development. Also, it helps if the programmer knows Ajax, because then he is already aware of the client/server communications details.

Hope this helps!
 
Ben Stanley
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks everyone. That's very helpful!
 
clojure forum advocate
Posts: 3479
Mac Objective C Clojure
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Ben Stanley wrote:Good to know! Unfortunately, I do not know C#


You don't have to know C# and as Federico said earlier, Java+Swing background is good plus.
 
Ranch Hand
Posts: 222
Google Web Toolkit Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
However I believe you should have some basic html/css/javascript knowledge since GWT is build on them.
 
Rancher
Posts: 436
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As Federico said, there are a lot of similiarities to Swing (or other desktop component frameworks). I think the result from the architecture is that a GWT programmer needs a deeper understanding for what he does.

When writing a (simple) page based web application (PHP, JSP only...) there are not that much places where a programmer can do serious mistakes. After the page is rendered, no fragments should remain, the request is closed, the client received some HTML, ideally no objects left.

When there is server-side state involved (e.g. Wicket) then accidentily serialising large objects (like data read from a DB... or the whole Spring context) can kill the server.

When using a technology that allows you to send Java objects to the client... unexperienced programmers may do this as it is easy. Just think of sending the User object directly from the database to the client... so a malicious client could read all the serialised fields - password hash, private states, internal ids... and it may even look clever at a first glance because you don't have to create extra DTOs. Plus you still have a server side to code, with an extra level of security risk.

So I think the more "state" there is the more insight a programmer needs. Client side state, whether fat client or something like GWT, adds an additional layer of risk and potential trouble - and in consequence requires more experience. Page based just is easier.
 
Bartender
Posts: 2326
100
Google Web Toolkit Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I do believe that CSS knowledge would definately be a catalyst for a great GWT application.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!