[
https://issues.apache.org/jira/browse/SCXML-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885840#comment-13885840
]
Woonsan Ko edited comment on SCXML-186 at 1/29/14 9:36 PM:
-----------------------------------------------------------
OK. It's better to have it as protected method now. I'm fine without '@' prefix
for the additional operators here.
Other than that, it's an impressive effort to achieve the bullet-point goals
above. Great work!
I had some difficulty in understanding between the lines. But now I think I
managed to understand the most of it and I'm impressed on how you solved the
serialization/deserialization issues with regard to script closure instances
with reasonable limitation (excluding closure instances), groovy base class
support even with <script> element option, more cleanups, etc.
Cheers, Woonsan
was (Author: woon_san):
OK. It's better to have it as protected method now. I'm fine without '@' prefix
for the additional operators here.
Other than that, it's an impressive effort. Great work!
I had some difficulty in understanding between the lines. But now I think I
managed to understand the most of it and I'm impressed on how you solved the
serialization/deserialization issues with regard to script closure instances
with reasonable limitation (excluding closure instances), groovy base class
support even with <script> element option, more cleanups, etc.
Cheers, Woonsan
> Groovy expression evaluator
> ---------------------------
>
> Key: SCXML-186
> URL: https://issues.apache.org/jira/browse/SCXML-186
> Project: Commons SCXML
> Issue Type: New Feature
> Reporter: Woonsan Ko
> Assignee: Ate Douma
> Fix For: 2.0
>
>
> A Groovy expression evaluator for SCXML expression can offer richer
> functionality which cannot be supported by the other simpler expression
> evaluator.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
