Adapters-HowTo - Revision history

Anonymous at 13:14, 21 December 2012

2012-12-21T13:14:23Z

Anonymous at 13:58, 12 October 2012

2012-10-12T13:58:49Z

Anonymous at 13:50, 12 October 2012

2012-10-12T13:50:22Z

Anonymous at 13:49, 12 October 2012

2012-10-12T13:49:54Z

Anonymous at 13:48, 12 October 2012

2012-10-12T13:48:01Z

Anonymous at 13:39, 12 October 2012

2012-10-12T13:39:57Z

Anonymous at 09:52, 12 October 2012

2012-10-12T09:52:01Z

Anonymous at 15:15, 9 October 2012

2012-10-09T15:15:36Z

Anonymous at 15:15, 9 October 2012

2012-10-09T15:15:13Z

Anonymous: /* Interfaces: call enqueue e dequeue */

2012-10-09T14:50:21Z

‎Interfaces: call enqueue e dequeue

@@ Line 16: / Line 16: @@
 </syntaxhighlight>
 for the [[DataHandler]].
-The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.
+The Operation interface has three subinterfaces: CallOperation, [[VCLEnqueueOperation|EnqueueOperation]] and [[VCLDequeueOperation|DequeueOperation]], all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.
   '''Please note:''' When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one.
   The buffer contains the input/output data for all the workflow operations, thus the output has to be ''added'' into the buffer so that the [[Core]] is
   able to know the status and data of each operation, reporting on it and reproducing it in case of need.

@@ Line 18: / Line 18: @@
 The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.
-  When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one.
+  '''Please note:''' When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one.
   The buffer contains the input/output data for all the workflow operations, thus the output has to be ''added'' into the buffer so that the [[Core]] is
   able to know the status and data of each operation, reporting on it and reproducing it in case of need.

← Older revision		Revision as of 13:50, 12 October 2012
Line 19:		Line 19:

	When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one.		When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one.
−	The buffer contains the input/output data for all the workflow operations, thus the output has to be ''added'' into the buffer so that the [[Core]] is able to know the status and data of each operation, reporting on it and reproducing it in case of need.	+	The buffer contains the input/output data for all the workflow operations, thus the output has to be ''added'' into the buffer so that the [[Core]] is
		+	able to know the status and data of each operation, reporting on it and reproducing it in case of need.

← Older revision		Revision as of 13:49, 12 October 2012
Line 18:		Line 18:
	The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.		The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.

−	When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one. The buffer contains the input/output data for all the workflow operations so the output has to be added into the buffer so that the [[Core]] is able to know the status and data of each operation, reporting on it and reproducing it in case of need.	+	When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one.
		+	The buffer contains the input/output data for all the workflow operations, thus the output has to be ''added'' into the buffer so that the [[Core]] is able to know the status and data of each operation, reporting on it and reproducing it in case of need.

← Older revision		Revision as of 13:48, 12 October 2012
Line 18:		Line 18:
	The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.		The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.

−	When implementing a new adapter it's important to ~~respect this rule and return~~ the buffer ~~received, after having~~ added into it the ~~data concerning~~ the ~~operation performed. This gives {{GVESB}} core~~ the ~~ability to access all input~~ and ~~output~~ data of each operation in ~~a workflow reading the buffer~~.	+	When implementing a new adapter it's important not to create a new [[GVBuffer]] but to output data into the received one. The buffer contains the input/output data for all the workflow operations so the output has to be added into the buffer so that the [[Core]] is able to know the status and data of each operation, reporting on it and reproducing it in case of need.

@@ Line 2: / Line 2: @@
-== Plugin and Adapter ==
+== Adapter ==
 == Configuration Files ==
@@ Line 13: / Line 16: @@
 </syntaxhighlight>
 for the [[DataHandler]].
-The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output. When implementing a new adapter it's important to respect this rule and return the buffer received, after having added into it the data concerning the operation performed. This gives {{GVESB}} core the ability to access all input and output data of each operation in a workflow reading the buffer.
+The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output.

@@ Line 13: / Line 13: @@
 </syntaxhighlight>
 for the [[DataHandler]].
-The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output. When implementing a new adapter it's important to respect this rule and return the buffer received, after having added into it the data concerning the operation performed. This means that {{GV ESB}} core can have access to all input and output data of each operation in a workflow reading the buffer.
+The Operation interface has three subinterfaces: CallOperation, EnqueueOperation and DequeueOperation, all defined into it.greenvulcano.gvesb.virtual package. The first one represents a syncronous call, the last two are used when dealing with queues. The main method of these interfaces is perform(), that accepts a GVBuffer as input and returns the same GVBuffer as output. When implementing a new adapter it's important to respect this rule and return the buffer received, after having added into it the data concerning the operation performed. This means that {{GVESB}} core can have access to all input and output data of each operation in a workflow reading the buffer.

@@ Line 3: / Line 3: @@
 == Plugin and Adapter ==
 == Configuration Files ==
 == Interfaces methods ==
-The Operation interface and its subinterface CallOperation have to be implemented each time a new GVVCL object is designed to make a call to an external system.
+The Operation interface has to be implemented each time a new GVVCL object is designed to make a call to an external system.
 The Node passed to the init() method is the one that we can find in the GVAdapters.xml configuration file. Each time you create an adapter you will add a section (node) into such file, like, for example:
 <syntaxhighlight lang="xml">
 <GVDataHandlerConfiguration name="DH_ENGINE" type="module" version="1.0">
 </syntaxhighlight>

← Older revision		Revision as of 14:50, 9 October 2012
Line 6:		Line 6:


−	== Interfaces: call enqueue e dequeue ==	+	== Interfaces: call enqueue and dequeue ==
−
−

	== Configuration Files ==		== Configuration Files ==