• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Bear Bibeault
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:
  • Frits Walraven
  • Himai Minh

Single page web applications - birth of yet another j2ee technology\framework?

 
Ranch Hand
Posts: 77
Eclipse IDE Java Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Already the number of frameworks and tools involved in developing j2ee web appplications is mind boggling.

Is this a new comer into this arena of j2ee technology terms? will this give birth to a new J2EE framework with a single jsp view, and a single servlet controller may be? are there any existing standards we can refer for creating a single page web app? is it all-AJAX to provide dynamic content within single page? am i asking too many questions in a single thread?
 
Sheriff
Posts: 67537
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This all has pretty much nothing to do with Java or JEE. SPAs are client-side apps, and what powers the backend is rather irrelevant.

You could use JSP to deliver a templated initial page, you could use servlets, or other JEE, to tend to the backend requests; but that's all implementation details.

I do not anticipate any additions to JEE just with SPAs in mind.
 
Author
Posts: 23
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
>> Already the number of frameworks and tools involved in developing j2ee web appplications is mind boggling.

Is this a new comer into this arena of j2ee technology terms?
Single page apps are really a client side development pattern more then anything. There are a ton of frameworks out there for this right now, but they are mostly JavaScript/Client side specific (Meteor/Derby are full stack). I prefer to use Node.js on the server side so that I can develop in the same language up and down the stack. I recently converted from a developer who sometimes did Ruby on Rails and sometimes Node.js to almost always doing Node.js because Ruby on Rails has been such a pain to configure and work through gem and deployment issues on.

Is there a place for Java in a Single Page App world? Certainly, the three major reasons I see to do Java.
1) You need massive Twitter level scale and need to convince the execs that you can support it. I don't know that Node.js cannot do this, I've just never done it.
2) You need your server side application code to interact with existing Java infrastructure. Unless you are building http interfaces for everything you need, I'm not aware of a technology that let's node.js make calls to Java code. (anyone know of any?)
3) Your development team are all Java developers and don't know much Javascript. Hire the JS experts for the front end, train some existing up, and set the rest loose on developing a Java http server. Or just move everyone over to Node.js and let those that don't want to do it quit.

That said, if you are starting from scratch on an internal application, a prototype for an app, a startup with no users, or even rewriting an app with moderately heavy traffic (LinkedIn scale), then Node.js seems to be the way to go. Not saying Node is perfect, not by any stretch of the imagination, it has plenty of pain points as well.

>> will this give birth to a new J2EE framework with a single jsp view, and a single servlet controller may be?
Possibly, but the http interface needs are so small that I've only seen people use existing libraries... people still use ruby on rails and just ignore the view code (unless they are using angular), or express for Node and ignore the view code. I haven't seen a popular server side framework developed specifically for single page apps, though Sinatra for Ruby may be the closest. It's really a small amount of code, no framework necessary.

>> are there any existing standards we can refer for creating a single page web app?
Absolutely, they are outlined in our book ;) I would rewrite them here, but the book is 450 pages long.

>> is it all-AJAX to provide dynamic content within single page?
Maaaybe. Usually. but you can also use web sockets and socket.io (also described in our book), and this can be the better choice depending on your use case.

>> am i asking too many questions in a single thread?
Nope.
 
Mohamed Iqzas
Ranch Hand
Posts: 77
Eclipse IDE Java Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you very much Josh Powell. You have answered all my questions (with patience) and now am clear what SPA really means. the book being promoted in HTML, CSS and JavaScript forum should have been a hint to me. But I just noticed. Really need to learn now.
 
Well THAT's new! Comfort me, reliable tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic