On Tuesday, October 16, 2012 9:25:59 AM UTC+2, Markus Backman wrote: > > Hi > > Where I work there is an ongoing debate on how the company should build > it's web applications in the future. The company is a large financial > company and the company has a large number of Java developers. The current > web applications is built upon Web 1.0 style, multipage and no AJAX. To > give the customers a better experience there is need to move to a Web > 2.0ish style with more of a singlepage application. > > The technology choice is being debated at the moment and the different > choices are: > * REST style JSON/XML services + some JavaScript framework(s) on the > client. > * Portlet 2.0 (JSR 286) + JSF 2.0 (JSR 314) > > There is no shortage of REST style + JS framework web applications out on > the Internet so that seems a rather popular approach. But what I haven't > found is some site that uses Portlet + JSF and combining it to a good Web > 2.0ish web application. Anyone that knows of such an application that can > point me in that direction? > > Any experiences and thought are welcomed. > The topic has been discussed in the past on this group. My experiences and view boils down to:
- Most Java front-end tech tend to rely far too much on session scope (JSF is a major sinner while GWT is an exception) and creates a massive dependency chain where complexity thrives. - No matter how well the browser aspect is abstracted away, you are *always* going to need some HTML/CSS/JavaScript skills anyway. - Consciously separating Model and ViewController at the transportation layer makes it easier to scale, allows you to mix technologies and even reuse the services for other things (say B2B scenario or a mobile client). So I would recommend spending a few hours with Jersey generating JSON, and jQuery Mobile building a simple UI consuming this JSON, to get a feeling for the approach I advocate. Services can be mocked simply by writing a piece of JSON and the simple dependency chain makes it super fast to compile and produces tight artifacts (your Java developers might develop a post-traumatic disorder but they still get to write Java services, servlet filters and create WAR's). /Casper PS: GWT is not bad, but the second item above still applies and it's can get quite slow to cross-compile a large project. GWT also has the problem that the POJO service request aspect is unpolished (notice how SmartGWT, GXT etc. all try to wrap their own incompatible mapping solutions). -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/jLLuxp7TMdcJ. 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/javaposse?hl=en.
