7.2 Application Object
| Description | An application in open-spaces is a collection of processing units.
|
Contained
Lists |
| 1 |
| Name | jar |
| Type | jar
|
| Description | The list of jarBases (including the processingUnitList and the gridJarList) within this application.
|
| Indexed property | name |
|
| |
| 2 |
| Name | processingUnit |
| Type | processingUnit
|
| Description | The list of jarBases (including the processingUnitList and the gridJarList) within this application.
|
| Indexed property | name |
|
| |
| 3 |
| Name | deploymentOption |
| Type | deploymentOption
|
| Description | The list of deployment-options for the application. The processing-unit can also have a list of deployment-options.
The deployment-options defined at the application level are the default options for the application as a whole. If the name and
location in the application deployment-option matches the name and location in the processing-unit deployment-option then the
processing-unit's deployment-option will take precedence.
|
| Indexed property | name |
|
|
Inherited
properties |
| template |
(base property)
| |
| text |
(base property)
| |
| jwpattern |
(base property)
| |
|
7.2.1 Property 'constraintExceptionType'
|
| Description | The constraintExceptionType is the type of the exception which is thrown if the constraint fails.
It can be any valid class name - probably defined by a 'jwclass'. It could be, for example, a specific class of business exception which should be thrown for this constraint.
If this is not in the same package as the build module (e.g. in the EJB Jar or Ear), then the name should be qualified by the package name.
The constraintExceptionType is available on constraints, objects and assemblies, and can also be set in the top level properties build file (e.g. build.jwp).
Because this is a delegated property, the actual value used is whichever instance is encountered first, working up from the validation object.
This means it is very easy to specialise the exceptions thrown in part of the specification tree (e.g. one session EJB), leaving the rest unchanged.
Failing any value at all, 'RuntimeException' is used ... but clearly this should not be used in production systems.
|
| Type | String |
7.2.2 Property 'customTemplateDirectory'
|
| Description | This only needs to be specified if you want to customize the standard generation templates for your requirements; you can ignore it otherwise.
If specified, this should be the template directory (equivalent to the standard resource/x/control level)
which defines the specific properties and templates you want to implement.
|
| Type | String |
7.2.3 Property 'description'
|
7.2.4 Property 'fifo'
|
| Description | This is the application-level default for the FIFO (first-in, first-out) property for JavaBeans.
As this is a delegated value, the 'fifo' properties in spaces and JavaBeans will
delegate up to the value - so it sets the default for all other objects.
The default for this value is normally false,
so JavaBeans in spaces will not be guaranteed to be read/taken in the same order they were written.
This follows the GigaSpaces defaults where fifo is false.
You can override this default by setting fifo=true in resources/giga-spaces/control/application/component.properties.
See customization 10 (in the directory jeewiz/customizations/giga-spaces).
|
| Type | boolean |
7.2.5 Property 'name'
|
| Description | The name for the Application EAR file.
|
| Type | String |
| Default | TheApplication |
7.2.6 Property 'package'
|
| Alias | namespace |
| Description | This is the package attribute: it declares the name of the package that this interface (or class, or entity, etc.) belongs to.
It can be used on
- reference types (interfaces and classes) and all their derivatives
- associations
- assemblies of model-objects
- containers of same, like jars.
It uses delegation of responsibility to search its parent chain. For example, in the J2EE realm, this means that the package can be specified on (working up the containment chain):
- an entity,
- or its ejb-jar,
- or the application,
- or in the assembly
- or in the build properties '.jwp' file.
If none of these is specified the package will be null.
Null packages are not recommended but legal for simple Java builds.
For larger systems, null packages are not allowed.
The combination of the package and class name (i.e. the fully-qualified Java classname) must be unique
across all reference types and their derivatives in a build.
|
| Type | String |
|
