|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (13)
View page history| {color:#ff0000}{*}{_}+(IN CONSTRUCTION)+{_}{*}{color} |
| h2. Processing Events Using Structured Stages |
... |
| \\ !WithoutStaging2.png|thumbnail! |
| We can see how this can become heavily linked as we add to the processing information. The goal of this exercise is to show how to use the external IEP process calling to avoid this.\\ |
| \\ |
h3. Technical Complexity |
... |
| If we were to do this in a single stage, this is what the process could look like: !iepWithoutStaging.PNG|thumbnail! |
| In the design section, we'll see what staging would do this interesting process...\\ |
| |
| h3. Design This design makes use of the iep external process calling. For this example, we would use only two stages. # Determination if the request comes from an employee or a client. |
| # Determination of the location of the request (which part of the world) to query the proper inventory database. \\ |
| \\ |
h4. Process Flow, Stage 1 |
| \\ !StagingFirstPart.PNG|align=center! |
| |
| \\ |
h4. Process Flow, Stage 2 |
| \\ !StagingSecondPart.PNG|align=center! |
| |
| \\ |
h4. Implementation Model |
... |
| h4. |
| \\ |
| * The Netbeans project for this example can be found [there|http://mediacast.sun.com/users/Serge_Blais/media/iepStagedEx1|Source code]. * A sample of a test message can be found in the test section of the composite application * A sql script to populate the DB is in the process files of the iep project. It has to be run *{_}after{_}* the deployment of the application. |
h3. Example Limitations |