RSB SCXML Engine: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732015-07-21T14:41:41ZOpen Source Collaboration Platform
Redmine Tasks #2348 (Feedback): Use reflections for nested RST typeshttps://code.cor-lab.de/issues/23482015-07-21T14:41:41ZD. Wiganddwigand@techfak.uni-bielefeld.de
<p>In order to use reflections for instantiating RST in java, the full package path is required.<br />For example to instantiate <strong>rst.kinematics.JointAngles</strong> the following path is needed: <strong>rst.kinematics.JointAnglesType$JointAngles</strong>. In order to ensure that nested types also work, Arne suggested to make use of domain knowledge regarding the structure of the dotted rst path. Since the package path is always lower case, the first upper case token has to be the parent type (confirmed by Johannes):<br /><strong>rst.euroc.ColoredPoseSet.ColoredPose.Color</strong> -> <strong>rst.euroc.ColoredPoseSetType$ColoredPoseSet$ColoredPose$Color</strong></p> Tasks #2337 (Feedback): Create parser for RST typeshttps://code.cor-lab.de/issues/23372015-07-01T14:40:05ZAnonymous
The <code>RSBDataParser</code> currenly only knows how to work with some primitive types, but since the rsb-ccordination DSL now also support all RST types, the <code>RSBDataParser</code> needs to be extended. Either:
<ul>
<li>by implementing separate parsers for all RST types (<em>not</em> cool) or</li>
<li>by implementing a generic RST parser (<em>cool!</em>)</li>
</ul>
<p>The second, cooler variant only works together when RST types DSL is propery integrated, because then SCXML is uniform.</p> Bug #2318 (New): State machine doesn't publish transition to initial statehttps://code.cor-lab.de/issues/23182015-06-03T15:55:16ZAnonymous
<p>The rsb scxml engine publishes all transition over the scope <code>/scxml-engine/statechange/</code> <strong>except</strong> the transition to the initial state.</p> Enhancement #2214 (New): repository for patched commons-scxmlhttps://code.cor-lab.de/issues/22142015-04-01T19:50:14ZM. Goerlichmgoerlic@techfak.uni-bielefeld.de
<p>Patching our version of the scxml executor became a monthly-task recently. To improve the handling of our code and tracability I would like to have a repository where our branch of the scxml library is located. Currently a binary is imported into the repository. For instance our current revision is 1658973 with a patch to fix "Cancel". Nobody really knows this actually.</p> Bug #2099 (Feedback): Engine has direct protobuf dependencieshttps://code.cor-lab.de/issues/20992014-11-21T13:17:42ZN. Kösternkoester@techfak.uni-bielefeld.de
<p>in RSXUtils.java is a reference to com.google.protobuf.Message which should not be necessary as this is a implementation detail from RST and should be fully encapsulated there. This will be important if there would be a switch from protobuf to any other lib at some point in the future. The rsb-scxml-engine would then break due to the direct protobuf dependency,see<br /><a class="external" href="http://opensource.cit-ec.de/issues/334">http://opensource.cit-ec.de/issues/334</a></p>
<p>For now we will delete the protobuf dependency from the rsb-scxml-engine, as the dependency will be resolved upstream via rst.</p> Bug #1992 (New): <rsb:wait> - Tag does not seem to be registered in the engine.https://code.cor-lab.de/issues/19922014-09-12T12:52:21ZD. Wiganddwigand@techfak.uni-bielefeld.de
<pre>
Sep 12, 2014 2:44:56 PM org.apache.commons.scxml2.io.SCXMLReader reportIgnoredElement
WARNING: Ignoring unknown or invalid element <wait> in namespace "http://opensource.cit-ec.de/rsb" as child of <onentry> at Line number = 23
<onentry>
<rsb:wait duration="2000"></rsb:wait>
</onentry>
</pre> Bug #1980 (New): Unable to create Listener with basic typehttps://code.cor-lab.de/issues/19802014-09-03T15:40:33ZN. Kösternkoester@techfak.uni-bielefeld.de
<p>The creation of a listener with a basic type as in</p>
<pre>
<transition event="RSBEventOnScope:/home/wardrobe/motionsensor" target="Human_Present">
<rsb:listener rsb:type="string" rsb:scope="/home/wardrobe/motionsensor"></rsb:listener>
</transition>
</pre>
<p>fails with:</p>
<pre>
java.lang.IllegalArgumentException: RST type 'string' does not exist
at rsb.scxml.RSXUtils.registerRstConverter(RSXUtils.java:35)
at rsb.scxml.RSBParticipantManager.startListener(RSBParticipantManager.java:42)
at rsb.scxml.Engine.instantiateTransitionListeners(Engine.java:145)
at rsb.scxml.Engine.start(Engine.java:163)
at rsb.scxml.EngineRunner.main(EngineRunner.java:53)
</pre>
<p>The engine should allow the creation of basic types .</p> Feature #1965 (In Progress): Implement custom action for RPC callshttps://code.cor-lab.de/issues/19652014-08-27T08:09:56ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>Realize custom action that handles method calls using the specification outlined in #1940.</p>
<p>It should be able to call methods:</p>
<ul>
<li>with the specified event data </li>
<li>utilizing referenced data model items</li>
<li>synchronously as default and optionally asynchronously</li>
</ul>
<p>Furthermore, we need to discuss how to handle return values and/or errors. Options:</p>
<ul>
<li>Raising events when returns arrive?</li>
<li>Writing return values to a specified slot in the datamodel</li>
<li>Something else?</li>
</ul> Feature #1962 (New): Support RSBs built-in datatypes in converter registrationhttps://code.cor-lab.de/issues/19622014-08-26T18:34:38ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>For instance, <code>string</code> datatypes in rsb:listener instances lead to exceptions as the engine tries to register the corresponding converters. This needs to be fixed and all built-in RSB datatypes should be supported in addition to RST-based types.</p> Enhancement #1949 (New): Remove waiting loophttps://code.cor-lab.de/issues/19492014-08-21T12:46:53ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Remove the waiting loop for the end of the executor with something that does not produce 1 second delay at max.</p>