Difference between revisions of "Adapters-HowTo"
| Line 16: | Line 16: | ||
== Interfaces methods == | == 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 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 Node passed to the init() method is the one that we can find in the | + | 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> | ||
Revision as of 14:49, 9 October 2012
This is intended as a mini guide for a developer who wants to create a new adapter for GreenVulcano® ESB.
Contents
Plugin and Adapter
Interfaces: call enqueue e dequeue
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 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:
<GVDataHandlerConfiguration name="DH_ENGINE" type="module" version="1.0">
