[
https://issues.apache.org/jira/browse/SCXML-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar updated SCXML-50:
-------------------------------
Fix Version/s: 1.0
Affects Version/s: 0.6
You're right, neither are. As noted in the last line of Section 6.5 of the WD
you mention, "Support for the <anchor> element is optional."
I'm tentatively setting the fix version to be v1.0 (next major release) since
this is not high on my priority list (though this is a genuine enhancement
request).
Some preliminary thoughts about implementing this feature:
* The o.a.c.s.SCInstance class will need to maintain a "snapshots" map
* Initially, the snapshots could be stored in their entirety, but this may be
resource intensive
* It may be possible to record mere deltas when appropriate, but this will
require more thought
* Snapshots can be taken directly off of the "contexts" map (at the minimum)
* Pieces of the datamodels should generally be Cloneable, but some thought
needs to be given about how offending bits should be treated (especially in the
root context -- error?)
* Some potential areas where spec clarifications are needed (what happens to
histories etc.)
> Add support for <anchor>
> ------------------------
>
> Key: SCXML-50
> URL: https://issues.apache.org/jira/browse/SCXML-50
> Project: Commons SCXML
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Chris Nack
> Fix For: 1.0
>
>
> "W3C Working Draft 21 February 2007" specifies both the <anchor> element, and
> the anchor attribute for the <transition> element. Neither appear to be
> supported by SCXML.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
