Difference between revisions of "Virtual Layer"
G.iannello (talk | contribs) (Created page with "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...") |
G.iannello (talk | contribs) m |
||
| Line 1: | Line 1: | ||
| − | It's the innovative and technological layer that provides to the entire platform the independence from any specific J2EE application server | + | 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 | ||
Revision as of 11:51, 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
