-
1. Re: expression or execute
kukeltje Sep 4, 2007 9:11 AM (in response to pmuir)nice topic, since more and more attributes in jdpl can contain 'expressions' (the subprocessname being the latest)
I do not see any objections to aliasing it and (making expression an alias of execute) and logging a warning about deprecation. But... Tom has the final say in it.
and if we are dicussing consistency and reuse, lets
- bring the identity module of jbpm in line with the one of the portal BUT not make jBPM dependend on the portal (sol it should be a separate project or under JBossSSO)
- Bring the frameworks used by projects in line (JSF, Flex, GWT)
- ....
:-D -
2. Re: expression or execute
tom.baeyens Sep 4, 2007 9:32 AM (in response to pmuir)alias is possible. deprecation is not good imo.
the hardest part is not to support the parsing, but making sure that the docs are a bit in sync and coherent. -
3. Re: expression or execute
pmuir Sep 4, 2007 2:12 PM (in response to pmuir)Why do you not like deprecation? Because you prefer expression to execute? Or because of keeping the language the same? Or...?
-
4. Re: expression or execute
tom.baeyens Sep 4, 2007 2:39 PM (in response to pmuir)i don't want to break current processes
-
5. Re: expression or execute
pmuir Sep 4, 2007 3:51 PM (in response to pmuir)I don't see why deprecation would break anything. The attribute would still work and as we are agreed on an alias wouldn't mean a code change (although it could, as Ronald suggested, print out a warning) - the difference would just be in the docs i.e.
expression - a Unified EL expression (deprecated, use execute)
execute - a Unified EL expression -
6. Re: expression or execute
kukeltje Sep 4, 2007 6:44 PM (in response to pmuir)Yes Tom, deprecation != removing :-P
-
7. Re: expression or execute
tom.baeyens Sep 5, 2007 2:53 AM (in response to pmuir)you're right. deprecating is more clear to the user what they should do.
and indeed ronald, it's the removing for which i was afraid. if we get to it, we deprecate the expression attribute, but we'll probably never remove it. -
8. Re: expression or execute
kukeltje Sep 5, 2007 4:39 PM (in response to pmuir)If we never intend to remove it, we should not really deprecate it (either by documenting it and/or logging a warning), just leave it in as an alias to execute.
-
9. Re: expression or execute
gavin.king Sep 5, 2007 8:22 PM (in response to pmuir)Deprecate it and then remove it in the next major version.
-