Difference between revisions of "Develop Generic VCL Call"
(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...") |
|||
| Line 18: | Line 18: | ||
in JBOSS_HOME/commons/lib | in JBOSS_HOME/commons/lib | ||
* log4j.jar | * 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. |
| + | |||
| + | [[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. | ||
| + | |||
| + | [[File:SetGVESBUserLibraries.png|border|800px]] | ||
==== | ==== | ||
Revision as of 11:50, 16 December 2012
Description
A VCL Generic Call is a facility to enable the use of custom Java libraries in GreenVulcano® ESB. The plug-in must implement the CallOperation interface and can be configured in GV Console® or 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 GreenVulcano® ESB 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, named "GVESB", as show in the image.
The create an Eclipse Java project (ex.GenericVCLCall) and add the GVESB User Libraries set to the project's classpath.
