Difference between revisions of "Virtual Layer"
G.iannello (talk | contribs) m |
G.iannello (talk | contribs) m |
||
| Line 2: | Line 2: | ||
* Makes no use of any proprietary mechanisms of any Application Server | * Makes no use of any proprietary mechanisms of any Application Server | ||
| − | * Performs ''virtual'' operations (such as dequeue, enqueue, forward and call) implemented by the | + | * Performs ''virtual'' operations (such as dequeue, enqueue, forward and call) implemented by the [[Core]] layer |
* Uses standard mechanisms for internal communication among components | * Uses standard mechanisms for internal communication among components | ||
Morever it separates the business analysis from the technical implementation and configuration | Morever it separates the business analysis from the technical implementation and configuration | ||
| − | * The business analyst can create the business flows through the Graphical Editor Console VulCon | + | * The business analyst can create the business flows through the Graphical Editor Console [[VulCon]] |
| − | * The technical specialist implements the flow through the configuration console GV Console | + | * The technical specialist implements the flow through the configuration console [[GV Console]] |
Revision as of 11:53, 8 February 2012
It's the innovative and technological layer that provides to the entire platform the independence from any specific J2EE application server
- Makes no use of any proprietary mechanisms of any Application Server
- Performs virtual operations (such as dequeue, enqueue, forward and call) implemented by the Core layer
- Uses standard mechanisms for internal communication among components
Morever it separates the business analysis from the technical implementation and configuration
- The business analyst can create the business flows through the Graphical Editor Console VulCon
- The technical specialist implements the flow through the configuration console GV Console
