[
https://issues.apache.org/jira/browse/SCXML-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar updated SCXML-111:
--------------------------------
Fix Version/s: 1.0
Makes sense. Setting fix version to next major release (v1.0) since any change
to the interface (which is not backwards compatible) will need to go into a
major release. I think both onsend and oncancel returning a Result POJO (that
may currently only contain success/failure notification but in future may
contain more information) may be the way to proceed here.
The v1.x line is the J6 branch is SVN. Trunk is the v0.x line.
> EventDispatcher interface should be independent from SCXMLExecutor
> ------------------------------------------------------------------
>
> Key: SCXML-111
> URL: https://issues.apache.org/jira/browse/SCXML-111
> Project: Commons SCXML
> Issue Type: Improvement
> Reporter: Ales Dolecek
> Priority: Minor
> Fix For: 1.0
>
>
> The SCXML requires that implemantations throw
> "send.failed.typenotsupported.stateid.sendid" if event "type" is not
> supported. The EventDispatcher interface however does not provide any means
> to figure out which SCXMLExecutor invoked the send (or cancel) method nor
> upon which Send object. This means that current EventDispatcher
> implementations must hold reference to SCXMLExecutor which prevents them from
> use with multiple instances (or handle all possible types).
> Passing SCXMLExecutor reference is not good solution since the
> EventDispatcher could interfere with current processin (eg. via chage to
> executor's context). Maybe the send method shoud return result indicating if
> the send invocation was "successfull". The cancel method might do likewise.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
