Dh-call - Revision history

Anonymous at 08:51, 20 November 2012

2012-11-20T08:51:09Z

Anonymous: /* Definition */

2012-11-12T11:52:44Z

‎Definition

Anonymous at 20:39, 30 March 2012

2012-03-30T20:39:21Z

Anonymous: /* Definition */

2012-02-27T10:29:54Z

‎Definition

Anonymous: /* VulCon / GV Console Configuration */

2012-02-14T17:28:22Z

‎VulCon / GV Console Configuration

Anonymous at 15:08, 10 February 2012

2012-02-10T15:08:12Z

Anonymous at 14:46, 9 February 2012

2012-02-09T14:46:21Z

Anonymous: /* VulCon / GV Console Configuration */

2012-02-09T14:37:44Z

‎VulCon / GV Console Configuration

Anonymous: moved Gvvcl-datahandler to Dh-call

2012-02-07T10:41:15Z

moved Gvvcl-datahandler to Dh-call

Anonymous: /* VulCon / GV Console Configuration */

2012-01-26T10:23:19Z

‎VulCon / GV Console Configuration

@@ Line 18: / Line 18: @@
 | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation
 |-
-| name || required || this field identifies the operation name that you will use in service definition.
+| name || required || This field identifies the operation name that you will use in service definition.
 |}

← Older revision		Revision as of 11:52, 12 November 2012
Line 2:		Line 2:

	A [[dh-call]] is the operation that must be configured into {{L_VULCON}} or {{L_GVCONSOLE}} [[System\|System section]], to define the parameters for making a call to the [[DataHandler]].		A [[dh-call]] is the operation that must be configured into {{L_VULCON}} or {{L_GVCONSOLE}} [[System\|System section]], to define the parameters for making a call to the [[DataHandler]].
		+
		+	The DBOBuilder to be invoked is defined by:
		+	* the input GVBuffer DH_SERVICE_NAME property value
		+	* the input GVBuffer.service field value

	==VulCon / GV Console Configuration==		==VulCon / GV Console Configuration==

@@ Line 1: / Line 1: @@
 ==Definition==
-A ''dh-call'' is an operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} [[System|System section]], to define the parameters for making a call to the [[DataHandler]].
 ==VulCon / GV Console Configuration==
-In order to add a ''dh-call'' operation you must define the following fields:
+In order to add a [[dh-call]] operation you must define the following fields:
 {|class="gvtable"
@@ Line 16: / Line 17: @@
 |}
-The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''dh-call'' operation:
+The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a [[dh-call]] operation:
 <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
@@ Line 33: / Line 34: @@
-To use a ''dh-call'' in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] into your [[Service]] element and define in the field ''operation-name'' the name defined in ''dh-call'' operation.
+To use a [[dh-call]] in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] into your [[Service]] element and define in the field ''operation-name'' the name defined in the [[dh-call]] operation.
-The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''dh-call'' operation in {{GVESB}} service:
+The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a [[dh-call]] operation in {{GVESB}} service:
 <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
@@ Line 50: / Line 51: @@
                      <Participant id-channel="CHANNEL-NAME" id-system="SYSTEM-NAME"/>
                      <Flow first-node="excel_reader" point-x="20" point-y="112">
-                         <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
+                         <GVOperationNode
-                                         dump-in-out="false" id="process"
+                              class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
-                                         id-system="GVESB" input="input"
+                              dump-in-out="false" id="process"
-                                         next-node-id="end" op-type="call"
+                              id-system="GVESB" input="input"
-                                         operation-name="TestInsertXML" output="output"
+                              next-node-id="end" op-type="call"
-                                         point-x="127" point-y="139" type="flow-node"/>
+                              operation-name="TestInsertXML" output="output"
                          <GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode"
-                                   end-business-process="yes" id="end" op-type="end"
+                              end-business-process="yes" id="end" op-type="end"
-                                   output="excel_xml" point-x="358" point-y="112"
+                              output="excel_xml" point-x="358" point-y="112"
-                                   type="flow-node"/>
+                              type="flow-node"/>
                      </Flow>
                  </Operation>
@@ Line 69: / Line 71: @@
-At this point you have configured a service with a ''dh-call'' operation.
+At this point you have configured a service with a [[dh-call]] operation.
-Into the ''dh-call'' it is possible to insert three elements:
+Into the [[dh-call]] it is possible to insert three elements:
-* Description
+* [[Description]]
 * [[Retriever Config]]
 * [[DBOBuilder]]

@@ Line 1: / Line 1: @@
 ==Definition==
-A ''dh-call'' is an operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} [[System section]], to define the parameters for making a call to the [[DataHandler]].
+A ''dh-call'' is an operation that must be configured into {{L_VULCON}} or  {{L_GVCONSOLE}} [[System|System section]], to define the parameters for making a call to the [[DataHandler]].
 ==VulCon / GV Console Configuration==

← Older revision		Revision as of 17:28, 14 February 2012
Line 33:		Line 33:


−	To use a ''dh-call'' in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] in [[Service ~~section~~]] and define in the field ''operation-name'' the name defined in ''dh-call'' operation.	+	To use a ''dh-call'' in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] into your [[Service]] element and define in the field ''operation-name'' the name defined in ''dh-call'' operation.

	The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''dh-call'' operation in {{GVESB}} service:		The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''dh-call'' operation in {{GVESB}} service:

@@ Line 3: / Line 3: @@
 ==VulCon / GV Console Configuration==
 In order to add a ''dh-call'' operation you must define the following fields:
-* ''type'': call. Unmodifiable. Used by the {{GVESB}} factory framework;
+{|class="gvtable"
-* ''class'': it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation;
+! Attribute !! Type !! Description
-* ''name'': this field identifies the operation name that you will use in service definition.
+|-
+| type || fixed || This attribute must assume the value '''call'''.
 The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a ''dh-call'' operation:

← Older revision	Revision as of 10:41, 7 February 2012
(No difference)