JBPM知识点------JPDL3.1规范
前言:
Class全类名
|
attribute
|
optional
|
the fully qualified classname of an implementation of org.jbpm.taskmgmt.def.AssignmentHandler
|
config-type配置类型
|
attribute
|
optional
|
{field|bean|constructor|configuration-property}. Specifies how the assignment-handler-object should be constructed and how the content of this element should be used as configuration information for that assignment-handler-object.
|
|
{content}
|
optional
|
the content of the assignment-element can be used as configuration information for your AssignmentHandler implementations. This allows the creation of reusable delegation classes. for more about delegation configuration, see Section 16.2.3, “Configuration of delegations”.
|
<target name="deploy.par">
<taskdef name="deploypar" classname="org.jbpm.ant.DeployParTask">
<classpath --make sure the jbpm-[version].jar is in this classpath--/>
</taskdef>
<deploypar par="build/myprocess.par" />
</target>
- cfg: cfg is optional, the default value is 'hibernate.cfg.xml'. The hibernate configuration file that contains the jdbc connection properties to the database and the mapping files.
- properties: properties is optional and overwrites *all* hibernate properties as found in the hibernate.cfg.xml
- createschema: if set to true, the jbpm database schema is created before the processes get deployed.
<action class="org.test.MyAction">
<city>Atlanta</city>
<rounds>5</rounds>
</action>
- 1) the class name (required) : the fully qualified class name of the delegation class.
<action class="org.test.MyAction">
- 2) configuration type (optional) : specifies the way to instantiate and configure the delegation object. By default the default constructor is used and the configuration information is ignored.
- 3) configuration (optional) : the configuration of the delegation object in the format as required by the configuration type.
- String doesn't need converting, of course. But it is trimmed.
- primitive types such as int, long, float, double, ...
- and the basic wrapper classes for the primitive types.
- lists, sets and collections. In that case each element of the xml-content is consitered as an element of the collection and is parsed, recursively applying the conversions. If the type of the elements is different from java.lang.String this can be indicated by specifying a type attribute with the fully qualified type name. For example, following snippet will inject an ArrayList of Strings into field 'numbers':
· <numbers>
· <element>one</element>
· <element>two</element>
· <element>three</element>
</numbers>
如,指定元素的属性
· <numbers>
· <element type="com.withub.cms.jbpm.assignmenthandler.WriteNewsAssignmentHandler">one</element>
· <element>two</element>
· <element>three</element>
</numbers>
<numbers>
<entry><key>one</key><value>1</value></entry>
<entry><key>two</key><value>2</value></entry>
<entry><key>three</key><value>3</value></entry>
</numbers>
- maps. In this case, each element of the field-element is expected to have one subelement key and one element value. The key and element are both parsed using the conversion rules recursively. Just the same as with collections, a conversion to java.lang.String is assumed if no type attribute is specified.
- org.dom4j.Element
- for any other type, the string constructor is used.
public class MyAction implements ActionHandler {
// access specifiers can be private, default, protected or public
private String city;
Integer rounds;
...
}
...
<action class="org.test.MyAction">
<city>Atlanta</city>
<rounds>5</rounds>
</action>
...
- taskInstance (org.jbpm.taskmgmt.exe.TaskInstance)任务实例
- processInstance (org.jbpm.graph.exe.ProcessInstance)业务程序实例
- processDefinition (org.jbpm.graph.def.ProcessDefinition)业务程序定义
- token (org.jbpm.graph.exe.Token)执行路径
- taskMgmtInstance (org.jbpm.taskmgmt.exe.TaskMgmtInstance)任务管理实例
- contextInstance (org.jbpm.context.exe.ContextInstance)上下文实例
<process-definition xmlns="urn:jbpm.org:jpdl-3.1">
...
</process-definition>
Name
属性,子元素是等价的
|
Type
|
Multiplicity
|
Description
|
name
|
Attribute
属性
|
Optional可以无名,版本-1
|
the name of the process
业务程序定义的名字
|
swimlane 泳道
泳道,表示业务程序的角色,用在任务分派中。
|
Element元素
|
[0..*]
0个或多个
|
the swimlanes used in this process. The swimlanes represent process roles and they are used for task assignments.
|
start-state
|
element
|
[0..1]
0个或1个
|
the start state of the process. Note that a process without a start-state is valid有效的, but cannot be executed.但不能执行
|
{end-state|state|node|task-node|process-state|super-state|fork|join|decision}
|
element
|
[0..*]
任意
|
the nodes of the process definition. Note that a process without nodes is valid, but cannot be executed.注意:一个业务程序没有节点是正确的,但不能被执行。
|
event 事件
process-start业务程序实例开始
process-end业务程序实例结束
<event type="process-start">
<action name="action1"></action>
</event>
|
Element元素
|
[0..*]
多个
|
the process events that serve as a container for actions
是动作的容器。
|
{action|script|create-timer|cancel-timer}
这些是全局定义的动作,脚本,创建定时器,取消定时器。它们必须有名字。可以被事件或转向所引用—通过名字。
|
element
|
[0..*]
|
global defined actions that can be referenced from events and transitions. Note that these actions must specify a name in order to be referenced.
|
task 任务
全局定义的任务,能够被在Action等中使用。
|
element
|
[0..*]
|
global defined tasks that can be used in e.g. actions.
|
exception-handler 异常处理器
一个异常处理器列表,用于处理所有在这个业务程序定义中被委派类抛出的异常。
|
element
|
[0..*]
|
a list of exception handlers that applies to all exceptions thrown by delegation classes thrown in this process definition.
|
Name
|
Type
|
Multiplicity
|
Description
|
{action|script|create-timer|cancel-timer}
一个定制的Action,代表这个节点的行为。
|
element
|
1
|
a custom action that represents the behaviour for this node
|
common node elements
公共节点元素
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
|
Description
|
Name节点名
|
attribute
|
required
|
the name of the node
|
Async异步
|
attribute
|
{ true | false }, false is the default
|
If set to true, this node will be executed asynchronously. See also Chapter 13, Asynchronous continuations
|
transition 转向
每一个离开转向,离开一个节点,都必须有一个明确的名字。只有一个离开转向,可以没有名字。第一个指定的转向是默认执行的转向。
|
element
|
[0..*]
|
the leaving transitions. Each transition leaving a node *must* have a distinct name. A maximum of one of the leaving transitions is allowed to have no name. The first transition that is specifed is called the default transition. The default transition is taken when the node is left without specifying a transition.
|
event 事件
支持事件类型:进入节点,离开节点
|
element
|
[0..*]
|
supported event types: {node-enter|node-leave}
|
exception-handler
|
element
|
[0..*]
|
a list of exception handlers that applies to all exceptions thrown by delegation classes thrown in this process node.
|
timer 定时器
监控这个节点的执行
|
element
|
[0..*]
|
specifies a timer that monitors the duration of an execution in this node.
|
Name
|
Type
|
Multiplicity
|
Description
|
name
|
attribute
|
optional
|
the name of the node
|
task 任务
这个任务开始一个新的业务程序的实例,或者捕获业务程序的发起者。
|
element
|
[0..1]
0或1个任务。
有特殊的用途。
|
the task to start a new instance for this process or to capture the process initiator. See Section 11.7, “Swimlane in start task”
|
event 事件
开始状态只有节点离开事件,没有节点进入事件。因为不能进入开始状态。
|
element
|
[0..*]
|
supported event types: {node-leave}
|
transition 转向
每一个离开转向必须有一个目标节点的名字
|
element
|
[0..*]
|
the leaving transitions. Each transition leaving a node *must* have a distinct name.
|
exception-handler
异常处理器
它们能够处理所有这个节点中的委派类抛出的异常
|
element
|
[0..*]
|
a list of exception handlers that applies to all exceptions thrown by delegation classes thrown in this process node.
|
Name
|
Type
|
Multiplicity
|
Description
|
name
|
attribute
|
required
|
the name of the end-state
|
event 事件
只有节点进入事件可用,因为无法离开。
|
element
|
[0..*]
|
supported event types: {node-enter}
|
exception-handler
处理这个节点中所有的Java处理类抛出的异常。
|
element
|
[0..*]
|
a list of exception handlers that applies to all exceptions thrown by delegation classes thrown in this process node.
|
Name
|
Type
|
Multiplicity
|
Description
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
|
Description
|
Signal信号
默认是last。就是全部任务完成后,执行默认转向
|
Attribute属性
|
optional
|
{unsynchronized异步|never从不|first第一个任务|first-wait|last全部任务|last-wait}, default is last. signal specifies the effect of task completion on the process execution continuation.
|
create-tasks
创建任务实例
默认是true。在执行任务节点时,创建任务节点的所有任务。也可以设为false。这样,你可以在运行时决定创建哪些任务实例。
此时,你可以在node-enter事件的处理ActionHandler中创建任务。当然,你也必须把create-tasks=”false”
|
attribute
|
optional
|
{yes|no|true|false}, default is true. can be set to false when a runtime calculation has to determine which of the tasks have to be created. in that case, add an action on node-enter, create the tasks in the action and set create-tasks to false.
|
end-tasks结束任务实例
默认false。如果设为true,离开该节点时,如果任务还没有结束,就关掉所有没关掉的任务实例。
|
attribute
|
optional
|
{yes|no|true|false}, default is false. In case remove-tasks is set to true, on node-leave, all the tasks that are still open are ended.
|
task 任务
当业务程序实例的执行进入该节点时,这些任务的实例会被创建
|
element
|
[0..*]多个
|
the tasks that should be created when execution arrives in this task node.
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
多样性
|
Description描述
|
sub-process
子业务程序,指定这个节点代表的子业务程序的定义(这样就不用在运行时指定实例了)
|
element
|
1
|
the sub process that is associated with this node
|
variable 变量
指定数据从父业务程序实例的RootToken到子业务程序的RootToken中,这会从子业务程序实例的生命周期。最后子业务程序实例结束时,会把变量传回并覆盖父业务程序的变量
|
element
|
[0..*]
|
specifies how data should be copied from the super process to the sub process at the start and from the sub process to the super process upon completion of the sub process.
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
|
Description
|
{end-state|state|node|task-node|process-state|super-state|fork|join|decision}
|
element
|
[0..*]
|
the nodes of the superstate. superstates can be nested.
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
|
Description
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
|
Description
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity多样性
|
Description
|
handler 处理器
只需要一个就够了。因为它返回决定采用的transition的名字
(2中用法:
1,指定DecisionHandler的实现类
2,EL表达式)
|
element
|
either a 'handler' element or conditions on the transitions should be specified
转向们应该指定一个处理器或者若干个条件
|
the name of a org.jbpm.jpdl.Def.DecisionHandler implementation
|
transition
转向
decision的转向能够使用条件。Decision将使用第一个条件=true的转向。没有条件的转向是true。
|
element
|
[0..*]多个
|
the leaving transitions. The leaving transitions of a decision can be extended with a condition. The decision will look for the first transition for which the condition evaluates to true. A transition without a condition is considered to evaluate to true (to model the 'otherwise' branch). See the condition element
|
common node elements
|
|
|
See common node elements
|
Name
|
Type
|
Multiplicity
|
Description
|
Type类型(事件的类型)
|
attribute
|
required
|
the event type that is expressed relative to the element on which the event is placed
|
{action|script|create-timer|cancel-timer}
响应这个事件的动作类型:ActionHandler,脚本(BeanShell脚本,不是条件的EL表达式),创建定时器,取消定时器
|
element
|
[0..*]
|
the list of actions that should be executed on this event
|
Name
|
Type
|
Multiplicity
|
Description
|
Name转向的名字
注意:每一个转向必须有一个目标名字。
|
attribute
|
Optional
可选
|
the name of the transition. Note that each transition leaving a node *must* have a distinct name.
|
To目标节点的名字
目标节点的等级名。节点的名字根据节点的作用域而来。类似于目录结构的命名规则。
如:
<state name="preparation"> <transition to="phase one/invite murphy"/> </state> <super-state name="phase one"> <state name="invite murphy"/> </super-state>
或:
<super-state name="phase one"> <state name="preparation"> <transition to="../phase two/invite murphy"/> </state> </super-state> <super-state name="phase two"> <state name="invite murphy"/> </super-state> |
attribute
|
required
|
the hierarchical name of the destination node. For more information about hierarchical names, see Section 9.6.3, “Hierarchical names”
|
{action|script|create-timer|cancel-timer}
在执行这个转向时执行的动作。因为transition不像Node那样本身有execute方法,必须通过动作来执行操作。
|
element
|
[0..*]
多个
|
the actions to be executed upon taking this transition. Note that the actions of a transition do not need to be put in an event (because there is only one)
|
exception-handler
|
element
|
[0..*]
|
a list of exception handlers that applies to all exceptions thrown by delegation classes thrown in this process node.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name名字
有名字的动作,可以被在业务程序定义中寻找。
|
attribute
|
Optional
可选
|
the name of the action. When actions are given names, they can be looked up from the process definition. This can be useful for runtime actions and declaring actions only once.
|
Class全类名
(action需要3者之一:全类名class,引用名ref-name,表达式)
|
attibute
|
either, a ref-name or an expression
|
the fully qualified class name of the class that implements the org.jbpm.graph.def.ActionHandler interface.
|
ref-name引用名
引用的动作的名字(让被引用的action处理)
|
attibute
|
either this or class
|
the name of the referenced action. The content of this action is not processed further if a referenced action is specified.
|
Expression表达式
类EL表达式指定方法
|
attibute
|
either this, a class or a ref-name
|
A jPDL expression that resolves to a method. See also Section 16.3, “Expressions”
|
accept-propagated-events接受传播事件
默认true。如果为false,那么action将仅仅在事件激发这个Action时执行。(事件会从低层次向高层次传递,直到process-definition。)同一个事件不会再被上层的action处理。即,事件在这个Action被销毁!
|
attribute
|
optional
|
{yes|no|true|false}. Default is yes|true. If set to false, the action will only be executed on events that were fired on this action's element. for more information, see Section 9.5.4, “Event propagation”
|
config-type配置类型
指定ActionHandler的实现类的对象应该怎样生成。其中的内容元素应该怎样用到action对象中。
|
attribute
|
optional
|
{field|bean|constructor|configuration-property}. Specifies how the action-object should be constructed and how the content of this element should be used as configuration information for that action-object.
|
Async异步
默认false。即,动作将在执行线程中同步执行。如果设为true,将发送执行这个action的消息到命令执行器,命令执行器将在一个独立的事务中同时/异步执行这个action。(处于业务程序实例主执行线程之外的线程中)
|
attibute
|
{true|false}
|
Default is false, which means that the action is executed in the thread of the execution. If set to true, a message will be sent to the command executor and that component will execute the action asynchonously in a separate transaction.
|
动作的内容应该作为你的ActionHandler实现类的配置信息。传递数据给ActionHandler实现类的对象。这允许你通过配置重用对象和组装对象。
|
{content}
|
Optional
可选
|
the content of the action can be used as configuration information for your custom action implementations. This allows the creation of reusable delegation classes. For more about delegation configuration, see Section 16.2.3, “Configuration of delegations”.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name脚本类型的动作的名字
有名字的脚本,可被查找。
(action的ref-name) |
attribute
|
optional
|
the name of the script-action. When actions are given names, they can be looked up from the process definition. This can be useful for runtime actions and declaring actions only once.
|
accept-propagated-events
接受传播事件
|
attribute
|
optional [0..*]
|
{yes|no|true|false}. Default is yes|true. If set to false, the action will only be executed on events that were fired on this action's element. for more information, see Section 9.5.4, “Event propagation”
|
expression 表达式
beanshell脚本。
如果没有指定variable脚本变量,那么你可以在表达式中使用当前Token(根Token,有fork-join,就有多条子token)的所有变量。也能够直接作为script的文本内容写表达式。不需要作为expression元素指定表达式
|
element
|
[0..1]
0或1个
|
the beanshell script. If you don't specify variable elements, you can write the expression as the content of the script element (omitting the expression element tag).
|
variable 脚本变量
如果不指定脚本变量,那么就会把当前Token上的所有变量都引进来,可以被表达式使用!如果指定了变量,那么在表达式中只能使用当前指定的这几个变量。
|
element
|
[0..*]
多个
|
in variable for the script. If no in variables are specified, all the variables of the current token will be loaded into the script evaluation. Use the in variables if you want to limit the number of variables loaded into the script evaluation.
|
Name
|
Type
|
Multiplicity
|
Description
|
|
{content}
|
|
a bean shell script.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name名字
业务程序变量(实际在各个token上,用当前token的)的名字
|
attribute
|
required
|
the process variable name
|
Access访问权
默认是:read,write。使用,分割。
read,write,required
|
attribute
|
optional
|
default is read,write. It is a comma separated list of access specifiers. The only access specifiers used so far are read, write and required.
|
mapped-name映射名
默认使用变量名。这指定变量名的一个别名。别名的意思,依赖于variable元素用在哪里。如果在script内,这是beanshell脚本变量的名字。任务的控制器内,这是任务参数的标签。如果在process-state内,这是子业务程序实例内的变量名。
|
attribute
|
optional
|
this defaults to the variable name. it specifies a name to which the variable name is mapped. the meaning of the mapped-name is dependent on the context in which this element is used. for a script, this will be the script-variable-name. for a task controller, this will be the label of the task form parameter and for a process-state, this will be the variable name used in the sub-process.
|
Name
|
Type
|
Multiplicity
|
Description
|
Expression
jPDL的EL表达式
返回的结果使用toString转换为一个String。应该是一个transition的名字。
|
attibute
|
either this or a class
|
A jPDL expression. The returned result is transformed to a string with the toString() method. The resulting string should match one of the leaving transitions. See also Section 16.3, “Expressions”.
|
Class类名
如果使用DecisionHandler而不是EL表达式。
|
attibute
|
either this or ref-name
|
the fully qualified class name of the class that implements the org.jbpm.graph.node.DecisionHandler interface.
|
config-type配置类型
(和ActionHandler中一样)
|
attribute
|
optional
|
{field|bean|constructor|configuration-property}. Specifies how the action-object should be constructed and how the content of this element should be used as configuration information for that action-object.
|
|
{content}
|
optional
|
the content of the handler can be used as configuration information for your custom handler implementations. This allows the creation of reusable delegation classes. For more about delegation configuration, see Section 16.2.3, “Configuration of delegations”.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name定时器的名字
如果不定义,就用所属节点的名字。
注意:每个定时器应该有唯一的名字。
|
attribute
|
optional
|
the name of the timer. If no name is specified, the name of the enclosing node is taken. Note that every timer should have a unique name.
|
Duedate期间(定时器启动到首次执行的时间)
指定创建定时器和执行定时器之间的时间间隔。
|
attribute
|
required
|
the duration (optionally expressed in business hours) that specifies the time period between the creation of the timer and the execution of the timer. See Section 14.1, “Duration” for the syntax.
|
Repeat重复(重复执行的间隔)
定时器执行之后,指定离开节点之前,定时器重复执行多少时间。
如果指定”yes””true”,则重复的间隔和启动定时期到执行的间隔duedate一样。
|
attribute
|
optional
|
{duration | 'yes' | 'true'}after a timer has been executed on the duedate, 'repeat' optionally specifies duration between repeating timer executions until the node is left. If yes or true is specified, the same duration as for the due date is taken for the repeat. See Section 14.1, “Duration” for the syntax.
|
Transition转向
激发定时器事件或者执行action之后,执行指定名字的转向。
|
attribute
|
optional
|
a transition-name to be taken when the timer executes, after firing the timer event and executing the action (if any).
|
cancel-event取消(定时器)(任务)事件
仅用于任务中的定时器。它指定哪个事件发生时,定时器应该被取消。默认是task-end事件。即,定时器所属的任务结束时,任务内的定时器会取消。
但你也能指定为task-assign,task-start。能够使用,给定多个取消定时器事件。
|
attribute
|
optional
|
this attribute is only to be used in timers of tasks. it specifies the event on which the timer should be cancelled. by default, this is the task-end event, but it can be set to e.g. task-assign or task-start. The cancel-event types can be combined by specifying them in a comma separated list in the attribute.
|
{action|script|create-timer|cancel-timer}
只有一个定时器激发的动作
|
element
|
[0..1]
0或1个
|
an action that should be executed when this timer fires
|
Name
|
Type
|
Multiplicity
|
Description
|
Name定时器的名字
|
attribute
|
optional
|
the name of the timer. The name can be used for cancelling the timer with a cancel-timer action.
|
Duedate延期时间
创建定时器和执行定时器的时间间隔
|
attribute
|
required
|
the duration (optionally expressed in business hours) that specifies the the time period between the creation of the timer and the execution of the timer. See Section 14.1, “Duration” for the syntax.
|
Repeat重复执行周期
如:yew/true,和延期时间相同。直到定时器取消(默认是离开该节点)
|
attribute
|
optional
|
{duration | 'yes' | 'true'}after a timer has been executed on the duedate, 'repeat' optionally specifies duration between repeating timer executions until the node is left. If yes of true is specified, the same duration as for the due date is taken for the repeat. See Section 14.1, “Duration” for the syntax.
|
Transition转向
定时器事件激发或者执行了定时器的动作之后,执行的转向
|
attribute
|
optional
|
a transition-name to be taken when the timer executes, after firing the the timer event and executing the action (if any).
|
Name
|
Type
|
Multiplicity
|
Description
|
Name被取消的定时器的名字
|
attribute
|
optional
|
the name of the timer to be cancelled.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name任务名字
|
attribute
|
optional
|
the name of the task. Named tasks can be referenced and looked up via the TaskMgmtDefinition
|
Blocking铁板一块?
默认false。如果为true,那么任务完成之后,才能离开节点。False,允许用户通过signal继续执行和离开节点。
|
attribute
|
optional
|
{yes|no|true|false}, default is false. If blocking is set to true, the node cannot be left when the task is not finished. If set to false (default) a signal on the token is allowed to continue execution and leave the node. The default is set to false, because blocking is normally forced by the user interface.
|
Signalling有信号功能
默认true,task能够通过end(transition)离开任务节点。
|
attribute
|
optional
|
{yes|no|true|false}, default is true. If signalling is set to false, this task will never have the capability of trigering the continuation of the token.
|
Duedate延迟时间(任务执行的的延迟时间)
|
attribute
|
optional
|
is a duration expressed in absolute or business hours as explained in Chapter 14, Business calendar
|
Swimlane泳道
指向一个泳道的名字。如果一个泳道指定在任务上,那么任务分派assignment将会被忽略!
(泳道也有assignment任务分派
)
|
attribute
|
optional
|
reference to a swimlane. If a swimlane is specified on a task, the assignment is ignored.
|
Priority优先权
|
attribute
|
optional
|
one of {highest, high, normal, low, lowest}. alternatively, any integer number can be specified for the priority. FYI: (highest=1, lowest=5)
|
assignment 任务分派
使用EL表达式或AssignmentHandler来分配任务。优先级低于swimlane
|
element
|
optional
|
describes a delegation that will assign the task to an actor when the task is created.
|
event 事件
task-assign任务分派事件,我们已经在TaskInstance中增加了previousActorId属性。表示原来的参与者
|
element
|
[0..*]
|
supported event types: {task-create|task-start|task-assign|task-end}. Especially for the task-assign we have added a non-persisted property previousActorId to the TaskInstance
|
exception-handler
|
element
|
[0..*]
|
a list of exception handlers that applies to all exceptions thrown by delegation classes thrown in this process node.
|
timer
|
element
|
[0..*]
|
specifies a timer that monitors the duration of an execution in this task. special for task timers, the cancel-event can be specified. by default the cancel-event is task-end, but it can be customized to e.g. task-assign or task-start.
|
controller 控制器
指定业务程序变量怎样传进任务变量。任务变量从GUI中由用户指定值。
|
element
|
[0..1]
|
specifies how the process variables are transformed into task form parameters. the task form paramaters are used by the user interface to render a task form to the user.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name名字
|
attribute
|
required
|
the name of the swimlane. Swimlanes can be referenced and looked up via the TaskMgmtDefinition
|
assignment 任务分配
指定这个泳道的任务分配器。它会在泳道的任务实例第一次被创建时执行。
|
element
|
[1..1]
必须且只有一个(但也有不指定的例子。应该是指所有人都可以)
|
specifies a the assignment of this swimlane. the assignment will be performed when the first task instance is created in this swimlane.
|
Name
|
Type
|
Multiplicity
|
Description
|
Expression
表达式
由于历史原因,它不是一个jPDL版EL表达式。相反,它是jBPM的身份组建的一个分配表达式。注意:这个实现依赖于jbpm身份组件。如果你不使用jBPM的身份组件,那么就不能使用它!
|
attribute
|
optional
|
For historical reasons, this attribute expression does not refer to the jPDL expression, but instead, it is an assignment expression for the jBPM identity component. For more information on how to write jBPM identity component expressions, see Section 11.11.2, “Assignment expressions”. Note that this implementation has a dependency on the jbpm identity component.
|
actor-id
参与者id
这是一个beanshell表达式。属性或方法返回一个String
|
attribute
|
optional
|
An actorId. Can be used in conjunction with pooled-actors. The actor-id is resolved as an expression. So you can refer to a fixed actorId like this actor-id="bobthebuilder". Or you can refer to a property or method that returns a String like this: actor-id="myVar.actorId", which will invoke the getActorId method on the task instance variable "myVar".
|
pooled-actors
参与者池。也是beanshell表达式。属性或方法返回一个String[],集合,或者,分割的参与者池的列表
|
attribute
|
optional
|
A comma separated list of actorIds. Can be used in conjunction with actor-id. A fixed set of pooled actors can be specified like this: pooled-actors="chicagobulls, pointersisters". The pooled-actors will be resolved as an expression. So you can also refer to a property or method that has to return, a String[], a Collection or a comma separated list of pooled actors.
|
Class全类名
|
attribute
|
optional
|
the fully qualified classname of an implementation of org.jbpm.taskmgmt.def.AssignmentHandler
|
config-type配置类型
|
attribute
|
optional
|
{field|bean|constructor|configuration-property}. Specifies how the assignment-handler-object should be constructed and how the content of this element should be used as configuration information for that assignment-handler-object.
|
|
{content}
|
optional
|
the content of the assignment-element can be used as configuration information for your AssignmentHandler implementations. This allows the creation of reusable delegation classes. for more about delegation configuration, see Section 16.2.3, “Configuration of delegations”.
|
Name
|
Type
|
Multiplicity
|
Description
|
Class全类名
|
attribute
|
Optional
可选
|
the fully qualified classname of an implementation of org.jbpm.taskmgmt.def.TaskControllerHandler
|
config-type配置类型
|
attribute
|
optional
|
{field|bean|constructor|configuration-property}. Specifies how the assignment-handler-object should be constructed and how the content of this element should be used as configuration information for that assignment-handler-object.
|
|
{content}
|
|
either the content of the controller is the configuration of the specified task controller handler (if the class attribute is specified. if no task controller handler is specified, the content must be a list of variable elements.
|
variable 任务变量
如果没有指定class属性,controller元素的内容必须是一些任务变量。Task中将可以使用它们。
|
element
|
[0..*]
|
in case no task controller handler is specified by the class attribute, the content of the controller element must be a list of variables.
|
Name
|
Type
|
Multiplicity
|
Description
|
Name子业务程序定义的名字
|
attribute
|
required
|
the name of the sub process. To know how you can test subprocesses, see Section 18.3, “Testing sub processes”
|
Version版本
默认为最新版
|
attribute
|
optional
|
the version of the sub process. If no version is specified, the latest version of the given process will be taken.
|
Name
|
Type
|
Multiplicity
|
Description
|
|
{content} or attribute expression
内容,或者属性EL表达式。
条件元素的内容是jPDL的EL表达式,返回true/false。
Decision将执行第一个表达式值为true的转向(次序依照processdefinition.xml中出现的先后顺序)。如果没有条件是真的转向,那么就会执行默认转向(第一个)
|
required
|
The contents of the condition element is a jPDL expression that should evaluate to a boolean. A decision takes the first transition (as ordered in the processdefinition.xml) for which the expression resolves to true. If none of the conditions resolve to true, the default leaving transition (== the first one) will be taken.
|
Name
|
Type
|
Multiplicity
|
Description
|
exception-class
异常类
指定要处理的可抛出(异常)类的全类名。如果不指定,那么就可以处理所有节点中ActionHandler等抛出的异常。
|
attribute
|
Optional
可选
|
specifies the fully qualified name of the java throwable class that should match this exception handler. If this attribute is not specified, it matches all exceptions (java.lang.Throwable).
|
action 动作
当异常处理器处理异常时,执行的动作。
|
element
|
[1..*]
1或多
|
a list of actions to be executed when an exception is being handled by this exception handler.
|
JBPM知识点------JPDL3.1规范相关推荐
- JPDL3.1规范手册
JPDL3.1规范手册 jBPM业务程序定义语言(jBPM Process Definition Language (JPDL)) ...
- jbpm知识点——tasknode
同fork等一样是一种节点类型.任务节点是jbpm中一个非常重要的概念,一个任务节点可以包含若干个任务(开始状态start-state只能有一个任务),不同的任务可以由不同的人来完成,任务实例被分配给 ...
- jbpm知识点——state
state是一种节点类型,当流程运行到该节点后会等待,需要外界进行触发,流程才能继续进行.一般用在同系统外部进行交互,如当流程进入该节点后向外系统发业务处理请求,然后进入等待状态,当外系统完成后发回响 ...
- J2EE工作流管理系统jBPM详解(二)
2008-11-21 作者:王铁民 来源:51CTO.com 子流程的使用 成果介绍 详细阐述开发成果 评审标准:清楚介绍开发成果 当一个流程的业务逻辑非常复杂的时候,可以考虑使用子流程.子流程和主流 ...
- 工作流-jbpm入门例子
原文地址:http://blog.csdn.net/hxirui/article/details/1221911 1. jBPM的简单介绍 jBPM是JBOSS下的一个开源java工作流项目 ...
- iKcamp|基于Koa2搭建Node.js实战(含视频)☞ 规范与部署
为什么80%的码农都做不了架构师?>>> 沪江CCtalk视频地址:https://www.cctalk.com/v/15114923889450 规范与部署 懒人推动社会进步 ...
- jbpm3\jbpm4_在jBPM中支持高级用户交互模式
jbpm3\jbpm4 许多通用业务流程包括人类参与者. 从简单的场景(例如人工批准)到涉及复杂的数据输入的复杂场景,人类活动都将新的方面(例如人类交互模式)引入到流程实现中. 人类交互模式的典型集合 ...
- Day1 命名规范 静态函数 构造析构 指针引用
WPS知识点_Day2 代码规范 命名 头文件 头文件包含顺序 头文件包含保护 注释 格式 作用域 运算符重载 不可重载的运算符 重载运算符两种定义 普通的非成员函数 定义为类成员函数 静态函数 st ...
- Liferay研究-smilingleo
http://blog.csdn.net/smilingleo/article/details/1859908 Liferay研究之一:Ext环境的搭建 本篇主要介绍如何搭建Ext开发环境.网上也有很 ...
最新文章
- 移动开发—HTML5 or Native?
- zblog文件大小超出,上传成功但插入不了
- 【算法python实现】 -- 岛屿的个数
- ML之DR之PCA:利用PCA对手写数字图片识别数据集进行降维处理(理解PCA)
- 进程线程003 模拟线程切换
- 占内存小的qq_手机内存空间告急,这些办法就能轻松搞定!
- Redis 04_位图bitmap
- 基于深度学习模型WideDeep的推荐
- “OpAfrica”行动:匿名者攻击南非武器采购机构
- java实现画布上画图
- nginx + tomcat + redis 部署项目,解决session共享问题。
- javacv相关学习:了解javacv
- FAT文件系统解析(一) 引导扇区、FAT表及根目录区分析
- 苏宁小店门店数量一年锐减428家 张近东之子张康阳为实控人
- 2018年南京公积金贷款新政答疑来了!首套房最高可贷50万元/人(附首套房认定标准)...
- C语言打印杨辉三角的多种方法
- 2023二建建筑施工备考第二天Day02
- pikachu之sql注入
- 胡凡算法笔记第二章摘录
- 计算机工资高的岗位,毕业五年后工资最高的4大专业,就业容易岗位多
热门文章
- Excel如何删除表中空白单元格整行
- 【汇正财经】如何进行股票板块的热点判断?
- IntelRealSense 深度相机 测量物体的实际长度 —— rs-measure 官网文档翻译
- 计算机路由表更新命令,计算机cmd命令之route,查看路由表,或配置一个更有效的路由...
- 笔记 -- 逆变电感设计3
- 3dsmax 里”编辑网格“与”编辑多边形“的区别
- originlab设置_Origin修改默认字体,提高作图效率!
- 《欧美剧集观看最佳索引》【2006-9-24更新】
- Linux自动化运维—LVS
- 续之前微信小程序的部分代码