Overview (Resoa Node - JSON/Rest Service Execution Container)

Most important packages
Package	Description
org.resoa.grid
org.resoa.node
org.resoa.rest

Other Packages
Package	Description
org.resoa.exception
org.resoa.node.core
org.resoa.node.core.test
org.resoa.topology
org.resoa.topology.service	This package contains the Resoa internal service implementations, defined within the resoa.topology.xsd.
org.resoa.util
org.resoa.util.cli

Resoa Nodes - Service Execution Container for grids/clouds

The central interface for all resoa node implementations is the ResoaGateway.

ResoaNodeGateway: Nodes act as a container for Resoa service implementations. You can deploy services on several nodes, Resoa will ensure that all nodes are linked by a Resoa stack managed connection (used by RestSession and resoa.persistence services).
ResoaNodeGateways will look for a GridInfo.xml file for setting up grid connections, if this file is not found, the node acts as a stand-alone service container.
RestServletContextListener: Use this class for enabling Resoa services within a web container. Check the info about WEB-INF/resoa.xml declaration files for more information about JSON/Rest to Java/Service mapping

ResoaServiceGateways offer a ResoaPersistence interface to every service implementation, this way a database storage is fully integrated within the framework. The resoa.persistence project offers a JSON based storage solution, running inside a Resoa grid.

Check the org.resoa.grid.GridFileBuilder class, it offers a generation of the GridInfo files for several Resoa nodes, including the resoa.stack .lcx files, required for connection security management