Grid configuration abstract

Preparing Service Domains for deployment

A service domain is a JAR file containing the XSD based object model and the service implementation classes.

The JAR file name defines the service domain name within the Resoa runtime management.
The naming convention is [domainname]-[version[].jar

Create resoa.xml file in META-INF of the JAR

resoa.xml example:

<Resoa xmlns="http://www.resoa.org/deploy" refreshable="true"
    persistentSeed="your optional AES seed">
	<!-- Service Permission declaration                      -->
	<service className="org.foo.Subscription">
		<roles>member</roles>
	</service>
	<service className="org.foo.User">
		<executions method="delete">
			<roles>admin</roles>
		</executions>
		<executions method="update">
			<roles>member</roles>
			<roles>admin</roles>
		</executions>
	</service>
	<!-- Persistence declaration                            -->
	<!-- User is persistent, we resolve the relation to Subscription -->
	<persistent className="org.foo.User" encrypted="true"keyMethod="getName">
		<relation fieldName="subscriptions" type="CREATE_UPDATE"/>
	</persistent>	
	<!-- Subscription must be declared as persistent as well -->
	<persistent className="org.foo.Subscription" encrypted="false"keyMethod="getName">
	</persistent>
</Resoa>

Conventions of resoa.xml

Permissions for service invocation can be declared on class and/or on method level.
If a service is not listed in resoa.xml, access is granted for every request.
Resoa Persistent handles types only, if there is an entry in resoa.xml.