4:51 a.m.
instantiate user defined classes at parsing time
------------------------------------------------
Key: JBPM-2323
URL: https://jira.jboss.org/jira/browse/JBPM-2323
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0
In the beginning we'll only support stateless user code if the class is referenced in
the jPDL.
Of course, expressions will still be resolved at process execution time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2323) instantiate user defined classes at parsing time
[
https://jira.jboss.org/jira/browse/JBPM-2323?page=com.atlassian.jira.plug...
]
Tom Baeyens updated JBPM-2323:
------------------------------
Description:
In the beginning we'll only support stateless user code if the class is referenced in
the jPDL.
We'll only instantiate user classes during parsing of the process definitions.
We'll explicitly remove instantiating of user classes during process execution.
So injecting transactional resources in process definitions is not valid. (not sure if we
easily be able to detect and throw an exception for that)
Of course, expressions will still be resolved at process execution time.
was:
In the beginning we'll only support stateless user code if the class is referenced in
the jPDL.
Of course, expressions will still be resolved at process execution time.
instantiate user defined classes at parsing time
------------------------------------------------
Key: JBPM-2323
URL: https://jira.jboss.org/jira/browse/JBPM-2323
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0
In the beginning we'll only support stateless user code if the class is referenced in
the jPDL.
We'll only instantiate user classes during parsing of the process definitions.
We'll explicitly remove instantiating of user classes during process execution.
So injecting transactional resources in process definitions is not valid. (not sure if
we easily be able to detect and throw an exception for that)
Of course, expressions will still be resolved at process execution time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:53 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2323) instantiate user defined classes at parsing time
[
https://jira.jboss.org/jira/browse/JBPM-2323?page=com.atlassian.jira.plug...
]
Tom Baeyens resolved JBPM-2323.
-------------------------------
Resolution: Done
I've updated the parsing and documented
"
Various elements in the jPDL process language refer to a an object on which an interface
method will be invoked.
* event-listener
* custom
* java
* assignment-handler in task
* handler in decision
For all objects that are referenced by a class name, will be instantiated during parsing
time. Which implies that the objects have to be threadsafe. This is typically OK since
those objects are typically immutable.
Objects that are referenced by an expression are calculated dynamically.
"
instantiate user defined classes at parsing time
------------------------------------------------
Key: JBPM-2323
URL: https://jira.jboss.org/jira/browse/JBPM-2323
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0
In the beginning we'll only support stateless user code if the class is referenced in
the jPDL.
We'll only instantiate user classes during parsing of the process definitions.
We'll explicitly remove instantiating of user classes during process execution.
So injecting transactional resources in process definitions is not valid. (not sure if
we easily be able to detect and throw an exception for that)
Of course, expressions will still be resolved at process execution time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5488
days inactive
5505
days old
2 comments
1 participants
participants (1)
-
Tom Baeyens (JIRA)