Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution:
Out of Date
-
Affects Version/s: jBPM 3.0.0
-
Fix Version/s: None
-
Component/s: Runtime Engine
-
Labels:None
-
Forum Reference:
Description
The jBPM documentation, section 7.4.5. Script, says:
"... By default, all process variables are available as script-variables and no script-variables will be written to the process variables."
But the transient variables are not available to <script>s, just to <action>s.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
This issue is still present as of version 3.2.
I'd like to expose the services of Spring beans by injecting a list of named beans into the transient variables of individual process instances before signalling them. e.g. in beanshell I'd like this to work:
persistentVariable = transientSpringBean.findData(arg);
I've tried wrapping VariableResolver but this only affects EL, and is not a suitable alternative.
Simon Gibbs
added a comment - This issue is still present as of version 3.2.
I'd like to expose the services of Spring beans by injecting a list of named beans into the transient variables of individual process instances before signalling them. e.g. in beanshell I'd like this to work:
persistentVariable = transientSpringBean.findData(arg);
I've tried wrapping VariableResolver but this only affects EL, and is not a suitable alternative. 
resolve as out of date because of 12 month no activity