Difference between revisions of "GVWorkbenchConfig"
(→GVBuffer) |
|||
| Line 117: | Line 117: | ||
* [[Description]] | * [[Description]] | ||
* [[#GVBuffer|GVBuffer]] | * [[#GVBuffer|GVBuffer]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 10:12, 8 March 2012
Contents
GreenVulcano® ESB Configuration
The following table shows the GVWorkbenchConfig element's attributes:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attribute must assume the value module |
| name | fixed | This attribute must assume the value WORKBENCH |
GVWorkbenchConfig contains the sub-elements:
EJBTest
This elements defines the Test details. Every test uses a specific element for initialization.
The following table shows the EJBTest element's attributes:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attribute must assume the value test. |
| id | required | Test unique id.
The attribute's value can't be null. |
| class | required | Plug-in class invoking the EJB.
The attribute's value can't be null. |
| jndiName | required | JNDI name of the EJB to invoke.
The attribute's value can't be null. |
| fileNameOutput | optional | This attribute defines the absolute path of the file where Test program writes the test results |
| fileNameInput | optional | This attribute defines the absolute path of the file where Test program writes the test input data |
Might contain the sub-element:
defaultInternalField
This element defines the internal fields that by default are assigned to the Input GVBuffer.
The following table shows the defaultInternalField element's attributes:
| Attribute | Type | Description |
|---|---|---|
| fieldName | required | Internal field definition. |
| fieldValue | required | Internal field value. |
Might contain the sub-element Description.
Loop
Element for multiple tests on GreenVulcano® ESB.
The following table shows the Loop element's attributes:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attributes must assume the value loop. |
| id | required | This attribute must correspond to the id of the relative EJBTest. |
| className | required | Class name that contains the test object identified. |
| fileName | required | Complete file path of the output file for the multiple test
A fully qualified name is mandatory. |
Might contain the sub-elements:
Test
Test to be executed within the loop.
The following table shows the Test element's attributes:
| Attribute | Type | Description |
|---|---|---|
| enabled | required | Flag to enable the test in the loop. If set to 'No' the test will not be executed. |
| transaction | optional | This attribute specifies whether to insert the test in a transaction and how.
The attribute's admitted values are:
|
Might contain the sub-elements:
Input
This element is the input type of the test to be performed
The following table shows the Input element's attributes:
| Attribute | Type | Description |
|---|---|---|
| jndiName | required | EJB JNDI name |
Might contain the sub-elements:
