TeeTime issueshttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues2017-08-16T13:52:37+02:00https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/350Let threads start their execution not until receiving a sign by the scheduler2017-08-16T13:52:37+02:00Christian WulfLet threads start their execution not until receiving a sign by the schedulertry to use a similar/same methodology for both schedulerstry to use a similar/same methodology for both schedulersChristian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/348Fix FIXMEs2017-08-15T15:05:47+02:00Christian WulfFix FIXMEsChristian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/331Reconsider map with threads and exceptions for other scheduling approaches2017-06-14T12:49:45+02:00Christian WulfReconsider map with threads and exceptions for other scheduling approachesThere is no dedicated thread for a stage when using the global task queue scheduling. The following interface is thus suboptimal:
``teetime.framework.exceptionHandling.AbstractExceptionListenerFactory.createInstance(Thread)``
Same appli...There is no dedicated thread for a stage when using the global task queue scheduling. The following interface is thus suboptimal:
``teetime.framework.exceptionHandling.AbstractExceptionListenerFactory.createInstance(Thread)``
Same applies for ``Stage.setOwningThread``Version 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/319Rename AbstractRunnableStage2017-03-21T09:56:31+01:00Christian WulfRename AbstractRunnableStagesuggestions:
- AbstractStageExecutor
- AbstractStageRunnersuggestions:
- AbstractStageExecutor
- AbstractStageRunnerVersion 3.0https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/309Read exception message from properties file2017-01-21T08:36:09+01:00Christian WulfRead exception message from properties file```java
code:
new Exception( exceptionMessages.get(1002, args) )
file.properties:
1002 = SourcePort may not be null {<arg0>} {<arg1>}
``````java
code:
new Exception( exceptionMessages.get(1002, args) )
file.properties:
1002 = SourcePort may not be null {<arg0>} {<arg1>}
```https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/182Refactor port actions2016-02-22T14:28:10+01:00Christian WulfRefactor port actionsCurrent situation:
```java
public CreatePortAction(final ConfigurationContext context, final InputPort<T> inputPort) {
this.context = context;
this.inputPort = inputPort;
}
// ...
private void onOutputPortCreated(final...Current situation:
```java
public CreatePortAction(final ConfigurationContext context, final InputPort<T> inputPort) {
this.context = context;
this.inputPort = inputPort;
}
// ...
private void onOutputPortCreated(final OutputPort<? extends T> newOutputPort) {
//context.addThreadableStage();
//context.connectPorts();
INTER_THREAD_PIPE_FACTORY.create(newOutputPort, inputPort);
DYNAMIC_ACTUATOR.startWithinNewThread(inputPort.getOwningStage());
newOutputPort.sendSignal(new InitializingSignal());
newOutputPort.sendSignal(new StartingSignal());
// FIXME pass the new thread to the analysis so that it can terminate the thread at the end
}
```
Goal:
- Remove constants INTER_THREAD_PIPE_FACTORY and DYNAMIC_ACTUATOR and, perhaps, use ``context`ยด instead.
Problems to reach the goal:
- Methods of ``context`` are not accessible (package-private)Version 2.1