Develop Generic VCL Call - Revision history

G.dimaio at 15:08, 16 December 2012

2012-12-16T15:08:40Z

G.dimaio at 14:28, 16 December 2012

2012-12-16T14:28:11Z

G.dimaio at 13:12, 16 December 2012

2012-12-16T13:12:03Z

G.dimaio at 12:52, 16 December 2012

2012-12-16T12:52:04Z

G.dimaio at 11:50, 16 December 2012

2012-12-16T11:50:16Z

G.dimaio: Created page with "==Description== A VCL Generic Call is a facility to enable the use of custom Java libraries in {{GVESB}}. The plug-in must implement the CallOperation interf..."

2012-12-16T11:38:07Z

Created page with "==Description== A VCL Generic Call is a facility to enable the use of custom Java libraries in {{GVESB}}. The plug-in must implement the CallOperation interf..."

New page

==Description==
A VCL Generic Call is a facility to enable the use of custom Java libraries in {{GVESB}}.
The plug-in must implement the [[VCLCallOperation|CallOperation]] interface and can be configured in {{L_GVCONSOLE}} or {{L_VULCON}} through a simple configuration interface.

==Generic VCL Call life cycle==
A Generic VCL Call life cycle is the same as every VCL plug-in:
* the init method is called at instance creation time
* the perform method is called at every service invocation
* the cleanUp method is called after every perform invocation
* the destroy method is called at instance destruction time

==Configure the Eclipse workspace==
To develop the plug-in is needed to reference some {{GVESB}} libraries:
in GV_HOME/application/deploy/gvesb-javaee5-*.ear/lib
* gvbase-*.jar
* gvcore-*.jar
* gvvcl-*.jar
in JBOSS_HOME/commons/lib
* log4j.jar
The simplest mode is to define a User Libaries set as show in the image.
[[File:GVESBUserLibraries.png]]

====

@@ Line 197: / Line 197: @@
-===Plug-in configuration===
+==Plug-in configuration and testing==
 In a {{L_VULCON}} project insert a new generic-call operation and the required parameters:
@@ Line 225: / Line 225: @@
 then start {{GVESB}} server and deploy the service using the {{L_GVCONSOLE}}.
 Reload the GVCore.xml configuration file and invoke the deployed service <code>TestGenericCall</code> setting as input a lower-case string:

@@ Line 14: / Line 14: @@
 The simplest mode is to define a User Libaries set, named "GVESB", as show in the image.
-[[File:GVESBUserLibraries.png|border|800px]]
+[[File:GVESBUserLibraries.png|800px]]
 The create an Eclipse Java project (ex.<code>GenericVCLCall</code>) and add the GVESB User Libraries set to the project's classpath.
-[[File:SetGVESBUserLibraries.png|border|800px]]
+[[File:SetGVESBUserLibraries.png|800px]]
 ==Generic VCL Call life cycle==
@@ Line 31: / Line 31: @@
 In the Eclipse project create a class with the parameters as illustrated in the image:
-[[File:SampleGenericVCLClass.png|border|400px]]
+[[File:SampleGenericVCLClass.png|400px]]
 The example plug-in is a simple class that perform a toupper|tolowe|echo operation on a String input or optionally to cancel the input data.
@@ Line 75: / Line 75: @@
-===Plug-in initialization===
+===Plug-in initialization code===
 To read the plug-in's configuration parameters must be used the [[XMLConfig]] utility class.
@@ Line 122: / Line 122: @@
 </syntaxhighlight>
 The following code illustrate the plug-in logic execution:
 <syntaxhighlight lang="java5">
@@ Line 183: / Line 185: @@
+     }
 </syntaxhighlight>

@@ Line 77: / Line 77: @@
 ===Plug-in initialization===
 To read the plug-in's configuration parameters must be used the [[XMLConfig]] utility class.
 For the Generic VCL Call the XML node describing the configuration parameters is the following:
 <syntaxhighlight lang="xml">
@@ Line 86: / Line 87: @@
      </generic-call>
 </syntaxhighlight>
 The following code illustrate the plug-in initialization:
 <syntaxhighlight lang="java5">
@@ Line 117: / Line 119: @@
                      {"key", key.toString()}}, exc);
+         }
+     }
 </syntaxhighlight>

@@ Line 2: / Line 2: @@
 A VCL Generic Call is a facility to enable the use of custom Java libraries in {{GVESB}}.
 The plug-in must implement the [[VCLCallOperation|CallOperation]] interface and can be configured in {{L_GVCONSOLE}} or {{L_VULCON}} through a simple configuration interface.
 ==Configure the Eclipse workspace==
@@ Line 23: / Line 16: @@
 [[File:GVESBUserLibraries.png|border|800px]]
-The create an Eclipse Java project (ex.GenericVCLCall) and add the GVESB User Libraries set to the project's classpath.
+The create an Eclipse Java project (ex.<code>GenericVCLCall</code>) and add the GVESB User Libraries set to the project's classpath.
 [[File:SetGVESBUserLibraries.png|border|800px]]
-====
+==Generic VCL Call life cycle==

@@ Line 18: / Line 18: @@
 in JBOSS_HOME/commons/lib
 * log4j.jar
 The simplest mode is to define a User Libaries set as show in the image.
-[[File:GVESBUserLibraries.png]]
+The simplest mode is to define a User Libaries set, named "GVESB", as show in the image.
 ====