What is Resoa?

Let’s approach this question by two statements:

"Resoa is software architecture for business enterprise solutions, defined out of the client/web perspective. It meets “Cloud Computing” from Business Software side, not from the underlying hardware services."

"Resoa from the production runtime perspective is a collection of servers on different sites. Resoa defines 3 server characters for runtime environment: REST, NODES and CONTROLLERS. All available servers define the “grid topology” for your Java Business implementation."

Why not using EJB instead?

J2EE was not designed for Internet based services!
A lot of websites started by using technique like PHP or other server based application frameworks, coming up beside J2EE (like Spring). Why could these frameworks succeed beside the Sun J2EE architecture?
Obviously it was too complicated to develop and deploy a simple service, saying dynamically "hello user" to an user, which hits a button on a website.

Exactly this is the point: J2EE was designed from a backend view, and a "web interface called JSP" was put on top of this middleware only for internet accessibility. J2EE grew up in a time, where host and database based applications were the dinosaurs in the information technology.
Today's Internet business is mainly determined by the websites and the underlying services; nobody is interested what kind of technology really works behind.

Looking under the cover of the HTML/CSS/Javascript brings up a zoo of technologies, somehow providing the data the website needs. And it still causes big headache to develop a new site with a proper session and user right management from the scratch!