Difference between revisions of "Configuration Components"
Manuele.simi (Talk | contribs) (→Configuring the ServiceContext) |
Manuele.simi (Talk | contribs) (→Configuring the ServiceContext) |
||
| Line 27: | Line 27: | ||
At least, one port-type class in a gCore compliant service MUST: | At least, one port-type class in a gCore compliant service MUST: | ||
* extend the GCUBEStartupPortType | * extend the GCUBEStartupPortType | ||
| − | * be declared with the parameter <code><parameter name="loadOnStartup" value="true"/></code> in the '''deploy-server.wsdd''' file | + | * be declared with the parameter <code><parameter name="loadOnStartup" value="true"/></code> in the '''deploy-server.wsdd''' file in the etc folder under the service location. |
This port-type performs the ServiceContext initialisation. | This port-type performs the ServiceContext initialisation. | ||
gCore recommends that only one port-type extends the StartupPortType. If two (or more) port-types extend the GCUBEStartupPortType, you have to be aware that your service context is initialised twice. This is an overhead but not an issue for the gCore initialisation procedure. However, it could be a problem if a service performs specific initialisation actions in the service context events (like the onReady() or onInitialisation() callback methods) that are supposed to be executed only once. | gCore recommends that only one port-type extends the StartupPortType. If two (or more) port-types extend the GCUBEStartupPortType, you have to be aware that your service context is initialised twice. This is an overhead but not an issue for the gCore initialisation procedure. However, it could be a problem if a service performs specific initialisation actions in the service context events (like the onReady() or onInitialisation() callback methods) that are supposed to be executed only once. | ||
==== Configuring the Port-Type Context(s) ==== | ==== Configuring the Port-Type Context(s) ==== | ||
Revision as of 22:30, 1 June 2008
[coming soon]
Contents
Configure What?
[coming soon]
Profiles, JNDIs & Descriptors
[coming soon]
JNDIs
Each context can be configured with a JNDI section automatically loaded by gCore. Following the stack of contexts, we can configure:
- the GHN Context
- the Service Context
- the port-type Context
While the first one is global for each node and its configuration is under the GHN manager responsibility, the others are service-specific and MUST be taken into consideration when developing a new gCore compliant service. Per each service, there are:
- one and only one ServiceContext
- several port-type Contexts, depending on the service architecture and needs
Both the Service Context and the port-type Contexts can be configured with a dedicated service element in the file called deploy-jndi-config.xml and placed in the etc folder under the service location.
Configuring the ServiceContext
$The ServiceContext....
At least, one port-type class in a gCore compliant service MUST:
- extend the GCUBEStartupPortType
- be declared with the parameter
<parameter name="loadOnStartup" value="true"/>in the deploy-server.wsdd file in the etc folder under the service location.
This port-type performs the ServiceContext initialisation. gCore recommends that only one port-type extends the StartupPortType. If two (or more) port-types extend the GCUBEStartupPortType, you have to be aware that your service context is initialised twice. This is an overhead but not an issue for the gCore initialisation procedure. However, it could be a problem if a service performs specific initialisation actions in the service context events (like the onReady() or onInitialisation() callback methods) that are supposed to be executed only once.
