>> 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.