Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Upgrade Commons BeanUtils to v1.8.0 [ SCXML-97 ]. Also upgrade Commons Digester to v1.8.1.
Roll version to 0.10-SNAPSHOT
Towards a v0.9 RC.
Post v0.8 changes, roll versions, clear release notes for release++.
Prep for a v0.8 RC.
Try to improve the dependencies page on the m2 site by using myfaces-api:1.1.5. Also move the build.xml over to use the m2 repo.
Wire up the new issues test suite.
Roll version.
Time for v0.7 RC2.
Upgrade to JUnit 3.8.2. Thanks for Sebb <sebbaz AT gmail DOT com> for the nudge.
Roll back to 0.7-SNAP in preparation for 0.7 RC2.
Roll version.
Time for v0.7 RC1.
Revert to 3.8.1 (for JDK 1.4). Thanks to sebb <sebbaz at gmail dot com>.
Time to use a recent JUnit release.
Upgrade recommended version of Commons Logging to v1.1.1
Moving to TLP
Moving back :)
Moving to TLP
Roll version to 0.7-SNAPSHOT. Clean release notes, they will be continually updated hereon.
Towards a RC for v0.6
Recommend JEXL 1.1 SCXML-32
Up logging to 1.1 SCXML-32
Up Digester to 1.8 to get going on XPath namespace support. SCXML-32
Update license headers in source files per: http://www.apache.org/legal/src-headers.html Associated checkstyle and changelog updates as well.
Correct namespace URI for SCXML documents. There was a discrepancy between the digester (had the correct URI) and the SCXML class (had an incorrect URI). Update URIs in all examples and documentation. Change warrants a minor release, IMO, so roll to 0.6-SNAPSHOT.
Roll to a post 0.5 version.
Time for the Commons SCXML 0.5 release. Vote result: http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=115392663425586&w=2
RC3 now.
Time for 0.5-RC2
SCXML-13 SCXML doesn't compile using (Sun) JDK 1.5
Roll version to 0.5-RC2-SNAPSHOT
The first release of Commons SCXML will have a version number of 0.5 (this is meant to better convey the fact that the underlying W3C specification is still a Working Draft). Suggested by Niall Pemberton <niall DOT pemberton AT gmail DOT com>.
Time for 1.0 RC1.
Implemented <invoke> (Section 4.4) and its children <param> (Section 4.5) and <finalize> (Section 4.6) -- all sections from the January 06 W3C WD [ http://www.w3.org/TR/scxml/ ]. With this addition, Commons SCXML aligns with the Jan '06 WD. The primary addition is the Invoker interface, which is used to define the possible interactions between the parent state machine (executor) and the types of invocable activities. Invocable activities must first register an Invoker implementation class for the appropriate "targettype" (attribute of <invoke>) with the parent SCXMLExecutor. The communication link between the parent state machine executor and the invoked activity is a bi-directional events pipe. All events triggered on the parent state machine get forwarded to the invoked activity. The processing semantics for these events depend upon the "targettype", and thereby vary per concrete implementation of the Invoker interface. The Invoker "lifecycle" is outlined below: * Instantiation via Class.newInstance() (Invoker implementation requires accessible constructor). * Configuration (setters for parent state ID and SCInstance). * Initiation of invoked activity via invoke() method, passing the source URI and the map of params. * Zero or more bi-directional event triggers. * Either completion or cancellation. These additions introduce backwards incompatible changes to the SCXMLSemantics interface (two new methods). I will bring up the couple of open issues (such as event names TBD in WD and handling invocation failure) at the related W3C face to face meeting later this week.
Move scxml to proper
*.gif includes for test classes (such as the ones used by stopwatch UI). Regen'd ant build file as well.
Wire up the new packages to the tests, regen'd ant build file.
Added JEXL support for SCXML documents. The SCXML specification allows implementations to support multiple expression languages so SCXML documents can be used in varying environments. Commons SCXML already supports the use of EL, using Commons EL. That is useful in servlet container environments and web frameworks, indeed the first use cases for Commons SCXML have been such that the JSP/EL APIs have come in via the "provided" maven scope. However since Commons EL 1.0 implements the EL portions of the JSP 2.0 specification, the inherent tie-in between the EL and JSP APIs leaves Commons EL an undesirable choice outside the realm of web applications. JEXL expressions provide an alternative for using Commons SCXML in desktop applications, some compound document formats and server managed code. The implementation consists of implementations of the Commons SCXML Context and Evaluator interfaces which serve as adapters to the JEXL APIs. Some minor refactorings have been made to reuse any common code into utility classes and some classes not available in the public Commons SCXML API now have better names, IMO. Adding Commons JEXL 1.0 to the dependency list in the project POM and updating the ant build file as well.
Get ant to pick up the semantics tests.
Update ant build file.
Added license to build.xml, hopefully won't be gen'ing it too often.
Overwriting hand-written ant build file with maven gen'd one.
1) Corrected year in license for top level artifacts 2) Added source and wiki links to home page
1) Corrected package declarations 2) Removed author tags from Javadoc 3) Added build and site artifacts (ant as well as maven builds) 4) Propedits for scxml/trunk
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |