Difference between revisions of "Adding State"
From GCube System
Manuele.simi (Talk | contribs) (→Multi port-type service) |
Manuele.simi (Talk | contribs) (→Adding State) |
||
| Line 2: | Line 2: | ||
In the first part of this tutorial we have created a stateless service for simplicity. However, the most common patterns used when developing gCube services are the ones that allow to create stateful service. | In the first part of this tutorial we have created a stateless service for simplicity. However, the most common patterns used when developing gCube services are the ones that allow to create stateful service. | ||
In this part of the tutorial we see how to add a state to the SampleService. | In this part of the tutorial we see how to add a state to the SampleService. | ||
| − | == | + | == Towards a multi port-type service == |
To add a state we need firstly to add two new port-types to the SampleService: | To add a state we need firstly to add two new port-types to the SampleService: | ||
* one is dedicated to create a new stateful resource, the so-called ''Factory service'' port-type | * one is dedicated to create a new stateful resource, the so-called ''Factory service'' port-type | ||
| Line 65: | Line 65: | ||
== Building & Deploying == | == Building & Deploying == | ||
== A Test Client == | == A Test Client == | ||
| + | |||
| + | --[[User:Manuele.simi|Manuele.simi]] 23:59, 25 March 2008 (EET) | ||
Revision as of 22:59, 25 March 2008
Contents
Adding State
In the first part of this tutorial we have created a stateless service for simplicity. However, the most common patterns used when developing gCube services are the ones that allow to create stateful service. In this part of the tutorial we see how to add a state to the SampleService.
Towards a multi port-type service
To add a state we need firstly to add two new port-types to the SampleService:
- one is dedicated to create a new stateful resource, the so-called Factory service port-type
- the other one is dedicated to access and manage the state, the so-called Service instance port-type
For both, we need to perform the same steps done for the Stateless port-type:
- add the port-types to the profile file
- define the WSDL interface for each port-type
- provide the Java implementation of the two port-types
plus other specific steps that allow to manage stateful services.
WSDL interface for the factory service
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="Factory"
targetNamespace="http://acme.org/sample"
xmlns:tns="http://acme.org/sample"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:corefaults="http://gcube-system.org/namespaces/common/core/faults"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing" >
<import namespace="http://gcube-system.org/namespaces/common/core/faults" location="../gcube/common/core/faults/GCUBEFaults.wsdl"/>
<types>
<xsd:schema targetNamespace="http://acme.org/sample">
<xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/03/addressing" schemaLocation="../ws/addressing/WS-Addressing.xsd" />
<xsd:element name="logon" type="xsd:string" />
<xsd:element name="logonResponse" type="wsa:EndpointReferenceType"/>
</xsd:schema>
</types>
<message name="logonInputMessage">
<part name="request" element="tns:logon"/>
</message>
<message name="logonOutputMessage">
<part name="response" element="tns:logonResponse"/>
</message>
<portType name="FactoryPortType">
<operation name="logon">
<input message="tns:logonInputMessage"/>
<output message="tns:logonOutputMessage"/>
<fault name="fault" message="corefaults:GCUBEFaultMessage"></fault>
<fault name="fault" message="corefaults:GCUBEUnrecoverableFaultMessage"></fault>
<fault name="fault" message="corefaults:GCUBERetrySameFaultMessage"></fault>
<fault name="fault" message="corefaults:GCUBERetryEquivalentFaultMessage"></fault>
</operation>
</portType>
</definitions>
Implementation
Configuring JNDIs & Descriptors
Building & Deploying
A Test Client
--Manuele.simi 23:59, 25 March 2008 (EET)
