Difference between revisions of "TagStreamerArchitecture"
From RifidiWiki
(→class time) |
(→abstract class PathEntity) |
||
Line 35: | Line 35: | ||
===abstract class PathEntity=== | ===abstract class PathEntity=== | ||
− | * | + | * reference TimeObject |
− | * method processdata(batchitem) | + | * method processdata(batchitem) |
===class ReaderEntitiy extend PathEntity=== | ===class ReaderEntitiy extend PathEntity=== |
Revision as of 19:54, 21 January 2008
Contents
Load XML Handler
This is loading the needed Information form the XML Files. This consists of three different Files:
- The Scenario,
- The Components
- The InputData
It will have a main load-method() taking in three filenames
Component Manager
The ComponentManager is a universal Class for creating the Components and keeping track of them. You can get the instances of the readers by asking the componentManager. He will create the reader if needed or returning a connected instance to the reader.
Processor
Is the executing part. It runs the Scenarios by calling the processdata methods and doing the timing coming along with the pathItems. For doing that it needs to be a thread which can be interrupted at certain points.
Command Interface
This is providing the user with the commands
- start
- stop
- pause (implement later on)
- resume (implement later on)
- clean
- load
Data Objects
class Scenario
- field ID
- field numOfRuns
- ArrayList of PathItems
class PathItems
- field ID (tells the position of this PathItem in the array)
- class TimeObject
- PathEntity Object
abstract class PathEntity
- reference TimeObject
- method processdata(batchitem)
class ReaderEntitiy extend PathEntity
- reference to the UIReader
- override the processdata() method
class GPIListernEntity extend PathEntity
- reference to the UIReader
- override the processdata() method
class timeObject implements observer
- Reference to SuspendableTimer
- method start
- method stop
- method suspend
- method resume
- field min value
- field max value
- field (boolean) random
- set Observer