You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc-content/drools-docs/src/main/asciidoc/AuthoringAssets/decision-tables-con.adoc
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
[id='decision-tables-con']
1
+
[id='decision-tables-con_{context}']
2
2
= Decision tables
3
3
4
4
Decision tables are XLS or XLSX spreadsheets that you can use to define business rules in a tabular format and that you can upload to your project in {CENTRAL}. Each row in the spreadsheet is a rule, and each column is a condition, an action, or another rule attribute. After you create and upload your decision tables, the rules you defined are compiled into Drools Rule Language (DRL) rules as with all other rule assets.
Copy file name to clipboardExpand all lines: doc-content/jbpm-docs/src/main/asciidoc/BPMN2/Events-section.adoc
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ Represents a timer that can trigger one or multiple times after a given period o
66
66
A Timer Event should have one incoming connection and one outgoing connection.
67
67
The timer delay specifies how long the timer should wait before triggering the first time.
68
68
When a Timer Event is reached in the process, it will start the associated timer.
69
-
The timer is canceled if the timer node is canceled (e.g., by completing or aborting the enclosing process instance). Consult the section "`<<_sec.timers>>`" for more information.
69
+
The timer is canceled if the timer node is canceled (e.g., by completing or aborting the enclosing process instance). Consult the section "`<<_timers>>`" for more information.
70
70
The Timer Event contains the following properties:
71
71
72
72
* __Id__: The id of the node (which is unique within one node container).
Copy file name to clipboardExpand all lines: doc-content/jbpm-docs/src/main/asciidoc/DomainSpecificProcesses/Overview-section.adoc
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@ Before moving on to an example, this section explains what custom work items and
8
8
9
9
In short, we use the term _custom work item_ when we're describing a node in your process that represents a domain-specific task and as such, contains extra properties and is handled by a `WorkItemHandler` implementation.
10
10
11
-
Because it's a domain-specific __task__, that means that a _custom
11
+
Because it's a domain-specific __task__, that means that a _custom
12
12
work item_ is equivalent to a `<task>` or ``<task>``-type node in BPMN2.
13
13
However, a _``__WorkItem__``_ is also Java class instance that's used when a `WorkItemHandler` instance is called to complete the task or work item.
14
14
15
-
Depending on the BPMN2 editor you're using, you can create a custom work item definition in one of two ways:
15
+
Depending on the BPMN2 editor you're using, you can create a custom work item definition in one of two ways:
16
16
17
-
* If you're using __Designer__, then this means creating a MVEL based definition and adding the definition in Designer itself. A description of this can be found in the <<_sec.designer.workitems>> section in the <<_ch.designer>> chapter. Once this is done, a new service node will appear on the BPMN 2.0 palette.
18
-
* If you're using the _Eclipse BPMN 2.0 modeler plugin_ (which can be found http://eclipse.org/bpmn2-modeler/[here]), then you'll can modify the BPMN2 `<task>` or ``<task>``-type element to work with `WorkItemHandler` implementations. See the <<_sec.eclipse.task_nodes>> section in the <<_ch.eclipse_bpmn_plugin>> chapter.
17
+
* If you're using __Designer__, then this means creating a MVEL based definition and adding the definition in Designer itself. Once this is done, a new service node will appear on the BPMN 2.0 palette. For more information, see <<jBPMDesigner>>.
18
+
* If you're using the _Eclipse BPMN 2.0 modeler plugin_ (which can be found http://eclipse.org/bpmn2-modeler/[here]), then you'll can modify the BPMN2 `<task>` or ``<task>``-type element to work with `WorkItemHandler` implementations. For more information, see the <<jBPMEclipseModeler>> chapter.
19
19
20
20
21
21
[[_sec.workitemhandler.overview]]
@@ -25,7 +25,7 @@ A _work item handler_ is a Java class used to execute (or abort) work items.
25
25
That also means that the class implements the `org.kie.runtime.instance.WorkItemHandler` interface.
26
26
While jBPM provides some custom `WorkItemHandler` instances (listed below), a Java developer with a minimal knowledge of jBPM can easily create a new work item handler class with its own custom business logic.
27
27
28
-
Among others, jBPM offers the following `WorkItemHandler` implementations:
28
+
Among others, jBPM offers the following `WorkItemHandler` implementations:
29
29
30
30
* In the [path]_jbpm-bpmn2_ module, `org.jbpm.bpmn2.handler` package:
31
31
+
@@ -38,11 +38,11 @@ Among others, jBPM offers the following `WorkItemHandler` implementations:
38
38
There are a many more `WorkItemHandler` implementations present in the [path]_jbpm-workitems_ module.
39
39
If you're looking for specific integration logic with Twitter, for example, we recommend you take a look at the classes made available there.
40
40
41
-
In general, a ``WorkItemHandler``'s `$$.$$executeWorkItem(...)` and ``$$.$$abortWorkItem(...)`` methods will do the following:
41
+
In general, a ``WorkItemHandler``'s `$$.$$executeWorkItem(...)` and ``$$.$$abortWorkItem(...)`` methods will do the following:
42
42
43
43
. Extract information about the task being executed (or aborted) from the `WorkItem` instance
44
44
. Execute the necessary business logic. This might be mean interacting with a web service, database, or other technical component.
45
-
. Inform the {ENGINE} that the work item has been completed (or aborted) by calling one of the following two methods on the `WorkItemManager` instance passed to the method:
45
+
. Inform the {ENGINE} that the work item has been completed (or aborted) by calling one of the following two methods on the `WorkItemManager` instance passed to the method:
@@ -133,7 +133,7 @@ A kmodule can contain multiple (1..n) kbase elements.
133
133
134
134
135
135
When defining a KieBase or a KieSession, you have the option of declaring a scope for that bean.
136
-
For example, To force Spring to produce a new bean instance each time one is needed, you should declare the bean's scope attribute to be 'prototype'. Similar way if you want Spring to return the same bean instance each time one is needed, you should declare the bean's scope attribute to be 'singleton'.
136
+
For example, To force Spring to produce a new bean instance each time one is needed, you should declare the bean's scope attribute to be 'prototype'. Similar way if you want Spring to return the same bean instance each time one is needed, you should declare the bean's scope attribute to be 'singleton'.
137
137
138
138
=== IMPORTANT NOTE
139
139
@@ -144,7 +144,7 @@ For proper initialization of the kmodule objects (kbase/ksession), it is mandato
@@ -231,7 +231,7 @@ The same tag is used to define both Stateful (__org.kie.api.runtime.KieSession__
231
231
232
232
233
233
When defining a KieBase or a KieSession, you have the option of declaring a scope for that bean.
234
-
For example, To force Spring to produce a new bean instance each time one is needed, you should declare the bean's scope attribute to be 'prototype'. Similar way if you want Spring to return the same bean instance each time one is needed, you should declare the bean's scope attribute to be 'singleton'.
234
+
For example, To force Spring to produce a new bean instance each time one is needed, you should declare the bean's scope attribute to be 'prototype'. Similar way if you want Spring to return the same bean instance each time one is needed, you should declare the bean's scope attribute to be 'singleton'.
235
235
236
236
=== Kie:ReleaseId
237
237
@@ -599,7 +599,7 @@ kie-spring provides features to define the listeners as standalone (individual)
Spring 3.1 introduces a new profile attribute to the beans element of the spring-beans schema.
1022
1022
This attribute acts as a switch when enabling and disabling profiles in different environments.
1023
1023
One potential use of this attribute can be to have the same kbase defined with debug loggers in 'dev' environment and without loggers in 'prod' environment.
1024
1024
1025
-
The below code snippet illustrates the concept of 'profiles'.
1025
+
The below code snippet illustrates the concept of 'profiles'.
As shown above, the Spring XML contains the definition of the profiles.
1059
-
While loading the _ApplicationContext_ you have to tell Spring which profile you`'re loading.
1059
+
While loading the _ApplicationContext_ you have to tell Spring which profile you`'re loading.
1060
1060
1061
-
There are several ways of selecting your profile and the most useful is by using the "spring.profiles.active" system property.
1061
+
There are several ways of selecting your profile and the most useful is by using the "spring.profiles.active" system property.
1062
1062
1063
1063
[source]
1064
1064
----
@@ -1067,15 +1067,15 @@ ApplicationContext ctx = new ClassPathXmlApplicationContext("beans.xml");
1067
1067
----
1068
1068
1069
1069
1070
-
Obviously, it is not a good practice to hard code things as shown above and the recommended practice is to keep the system properties definitions independent of the application.
1070
+
Obviously, it is not a good practice to hard code things as shown above and the recommended practice is to keep the system properties definitions independent of the application.
1071
1071
1072
1072
[source]
1073
1073
----
1074
1074
-Dspring.profiles.active="development"
1075
1075
----
1076
1076
1077
1077
1078
-
The profiles can also be loaded and enabled programmtically
1078
+
The profiles can also be loaded and enabled programmtically
1079
1079
1080
1080
[source]
1081
1081
----
@@ -1095,11 +1095,7 @@ This chapter describes the infrastructure used when configuring a human task ser
1095
1095
=== How to configure Spring with jBPM Human task
1096
1096
1097
1097
1098
-
The jBPM human task server can be configured to use Spring persistence. <<_kie_spring_human_task_example>>
1099
-
is an example of this which uses local transactions and Spring's thread-safe EntityManager proxy.
1100
-
1101
-
The following diagram shows the dependency graph used in <<_kie_spring_human_task_example>>
1102
-
.
1098
+
The jBPM human task server can be configured to use Spring persistence. The following is a dependency graph for a configuration that uses local transactions and Spring's thread-safe EntityManager proxy:
1103
1099
1104
1100
.Spring Human Task integration injection dependencies
0 commit comments