[JBoss Seam] - JBPM-Timer cannot be started with Seam
by Premheiko
Hey,
I'm new to JBpm & Seam.
Could you please tell me how to start a timer? Is a Scheduler needed for this?
I have define a process definition :
| <?xml version="1.0"?>
| <process-definition name="MyProcess">
| <start-state name="start">
| <task name="start">
| <assignment pooled-actors="testP0"></assignment>
| </task>
| <transition name="to_P0" to="p0">
|
| </transition>
| </start-state>
| <task-node name="p0">
|
| <task name="task1">
| <assignment pooled-actors="testP0"></assignment>
| <event type="task-start">
| <action class="com....MyAction">
| <name>"#{workflowAction.nr}"</name>
| </action>
| </event>
| </task>
|
| <transition name="to_P1" to="P1"></transition>
| </task-node>
| <task-node name="P1">
| <task name="task1">
| <assignment pooled-actors="testP0"></assignment>
|
| <event type="task-start">
| <action class="com....MyAction">
| <name>#{workflowAction.nr}</name>
| </action>
| </event>
|
| </task>
| <transition name="zu_P2" to="P2" />
| </task-node>
| <task-node name="P2">
| <task name="task2">
| <assignment pooled-actors="testP0"></assignment>
| <timer name="QuarzTimer2" duedate="30 seconds"
| repeat="60 seconds">
| <action class="com.....TimerAction"/>
| </timer>
| </task>
| <transition name="to_P3" to="P3"></transition>
| </task-node>
| <task-node name="P3">
| <task name="task3"></task>
| <transition name="to_P4" to="P4"></transition>
| </task-node>
| ........
|
2 problems :
-First ,the variable "name" cannot be stored correctly.
-Second:My Timer cannot be started
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027572#4027572
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027572
19Â years, 1Â month
[JBossCache] - PojoCache vs serialized bean in TreeCache
by bob_ninja
I am looking at both TreeCache and PojoCache for beans. My primary focus at the moment is performance of updates. The bean contains the usual mix of string and integer properties. Nothing fancy.
I am following the PojoCache examples to store my bean in a PojoCache. The alternative would be to serialize it and store byte[] in a TreeCache. In terms of modifications, about the worst case scenario (for TC) would be update to a boolean property which is encoded in an integer. Thus what happens when a single integer property is modified.
PojoCache using AOP updates the single attribute in the bean's node. The transaction will update bean's node.
The alternative is to serialize modified bean and put (update) it in tree cache. The transaction will update entire bean's serialized state.
The default logic is that single attribute update is cheaper/faster than entire serialized state.
However, my bean is simple (no child objects). It is about 170 bytes serialized. Serialization processing itself is fast, about 37 ns/bean on an average PC. Seems that the actual data content sent for replication purposes is minor between the 2 cases. So really performance is almost the same.
I do have another bean which is parent of this one. I would serialize them separately and update them individually. I could use special locking attributes to ensure atomic updates to parent and children.
The reason I am asking this is because I am not sure that the added complexity of PojoCache and aspects are worth the minor benefit. When I started using Hibernate it instrumented my beans automatically without extra compiling steps and classes (or at least very few classes). Also PojoCache seems to be still young and API is changing, so difficult to use. TreeCache is fairly simple.
Anyway let me know what ou think. thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027569#4027569
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027569
19Â years, 1Â month