[
http://jira.jboss.com/jira/browse/JBPM-72?page=comments#action_12367825 ]
Ronald van Kuijk commented on JBPM-72:
--------------------------------------
1: <variable name="bla" type="string" />
would only have runtime checking , as would
2: <variable name="bla" type="string"
value="blaValue"/>
What we could do is something like
3:
<variable name="bla">
<string>a string</string>
</variable>
and have elements for all default supported types. This can be checked design-time as
long as there are corresponding XSD types. One other option is to extend the eclipse xml
validator and make it aware of format #2 and check those... 3 would imo have the least
impact
required variable declaration
-----------------------------
Key: JBPM-72
URL:
http://jira.jboss.com/jira/browse/JBPM-72
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Priority: Optional
we could add support for a configuration that requires all variables to be declared
(including the type) before they are used. this creates a bit of 'type safety',
although it is only checkable at runtime...
this should be done on the level of the task. maybe tasks should be able to extract data
from the process and completion of the task should update the variables in the context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira