[JBoss Tools (users)] - Re: upgrade to WTP 2.0.2 breaks EAR deployment in JBoss Tool
by whitty69
I just updated the eclipse wst package today and it works.
fyi, Update history shows me this:
03.06.2008 15:15:18 org.eclipse.wst.common_sdk.feature_2.0.2.v200802150100-4-384H8HS6JCZyXYql06-5r3HoFL feature-install success
03.06.2008 15:17:27 org.eclipse.wst.common_core.feature.source_2.0.2.v200802150100-7C78EKOE_EkMNlO6f7cjpz0 feature-enable success
03.06.2008 15:17:27 org.eclipse.wst.common_ui.feature.source_2.0.2.v200802150100-7C5EH3E9RvTVnirrspVz0bmP7g8d feature-enable success
03.06.2008 15:17:27 org.eclipse.wst.common_sdk.feature_2.0.2.v200802150100-4-384H8HS6JCZyXYql06-5r3HoFL feature-enable success
03.06.2008 15:17:27 org.eclipse.jst.web_core.feature.patch2_2.0.2.v200803241913-208i8s733I395D6BA7 feature-install success
03.06.2008 15:17:27 org.eclipse.jst.web_core.feature.patch2_2.0.2.v200803241913-208i8s733I395D6BA7 feature-enable success
03.06.2008 15:17:27 org.eclipse.wst.xml_sdk.feature_2.0.2.v200802150100-4-384F4HNPHrjfp4eY0Myg0ZqZLI feature-install success
03.06.2008 15:17:30 org.eclipse.wst.xml_core.feature.source_2.0.2.v200802150100-787BE_4CYQCD-DaQMIfPd feature-enable success
03.06.2008 15:17:30 org.eclipse.wst.xml_ui.feature.source_2.0.2.v200802150100-7A1ECMCnbcl1bVs9uNm_Zkieb7Qe feature-enable success
03.06.2008 15:17:30 org.eclipse.wst.xml_sdk.feature_2.0.2.v200802150100-4-384F4HNPHrjfp4eY0Myg0ZqZLI feature-enable success
03.06.2008 15:17:30 org.eclipse.wst.sdk_2.0.2.v200802150100-7E-7E8aNek-SRfrjr6TqAZAYKdiU feature-install success
03.06.2008 15:17:37 org.eclipse.wst.server_core.feature.source_2.0.2.v200802150100-2-CN8s733H3_3Ic feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.server_ui.feature.source_2.0.2.v200802150100-77-CX9vCXDkvWGPlAMGMi447 feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.server_sdk.feature_2.0.2.v200802150100-4-384B2FiBz0GfGoyZIZvCcrZeJe feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.ws_core.feature.source_2.0.2.v200802150100-7E7KEB2EC3wSU5UghChM0v feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.ws_ui.feature.source_2.0.2.v200802150100-791ECIAufYO9BlarnPCFGewtZiN1 feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.ws_sdk.feature_2.0.2.v200802150100-4-384D4HNLFynbSBEnl1rhSbVadT feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.web_core.feature.source_2.0.2.v200802150100-42CN_kE77a8F9XCOEL feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.web_ui.feature.source_2.0.2.v200802150100-7A0EAlCiWfJKsCZoChvz0dMYOb feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.web_sdk.feature_2.0.2.v200802150100-4-384F3HLoHmeiNNvEk0Fz08lGMx feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.doc.isv.feature_2.0.2.v200802150100-1-Am7w311913312746 feature-enable success
03.06.2008 15:17:37 org.eclipse.wst.sdk_2.0.2.v200802150100-7E-7E8aNek-SRfrjr6TqAZAYKdiU feature-enable success
03.06.2008 15:17:37 org.eclipse.jst.sdk_2.0.2.v200802150100-7F-7D8fNerpqc2VheGP-mWEPz-u9 feature-install success
03.06.2008 15:17:55 org.eclipse.jst.common_core.feature.source_2.0.0.v200706041905-1007w311817231426 feature-enable success
03.06.2008 15:17:55 org.eclipse.jst.common_sdk.feature_2.0.0.v200706041905-4--7z53A46_4E5I5A38598x42292 feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.server_core.feature.source_2.0.2.v200802150100-56CQ9rC7EK_UAblGAD2537 feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.server_ui.feature.source_2.0.2.v200802150100-77-CT9yJXEkuiKVeQrclqTHQ3648 feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.server_sdk.feature_2.0.2.v200802150100-4-384B2FeC1NfHoxlMfoT67ypqsi feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.server_adapters.feature.source_2.0.2.v200802150100-787KE8iDUUEF6GwKwpHEQ feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.server_adapters.sdk.feature_2.0.2.v200802150100-4-384C_NPAnHcXII9J4W5AZQ_EVV feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.web_core.feature.source_2.0.300.v200802200333-7Q7AE7JEHhHeh0hI5y-QGB feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.web_ui.feature.source_2.0.2.v200802150100-7B1DzCkuNa_RPevwkwB1iJ6z-0RH feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.web_sdk.feature_2.0.2.v200802150100-5-490K6JGI--ZdDUSh49pBBHUEXa feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.enterprise_core.feature.source_2.0.2.v200802150100-42Au_kE77c7EAgE7I7 feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.enterprise_ui.feature.source_2.0.2.v200802150100-7b7_Es8EU6AXOV9QLJSees1SQoYQ feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.enterprise_sdk.feature_2.0.2.v200802150100-4-384g_CPvCIc9EaRXJ3VWlXq8Yb feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.doc.isv.feature_2.0.2.v200802150100-1-Aj7w311913312746 feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.webpageeditor.feature.source_1.0.1.v200709110605-3-29oA55P5V8A feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.webpageeditor_sdk.feature_1.0.1.v200709110605-2-18045ByDG9T8eAI0403_pB66Q6 feature-enable success
03.06.2008 15:17:56 org.eclipse.jst.sdk_2.0.2.v200802150100-7F-7D8fNerpqc2VheGP-mWEPz-u9 feature-enable success
03.06.2008 15:17:56 org.eclipse.jpt_sdk.feature_1.0.2.v200802140100-2-384B2_KFdUJG6FdNiMJMQDZRDE feature-install success
03.06.2008 15:17:57 org.eclipse.jpt.feature.source_1.0.2.v200802140100-77-7_CYQCD2CaLYCHCD feature-enable success
03.06.2008 15:17:57 org.eclipse.jpt_sdk.feature_1.0.2.v200802140100-2-384B2_KFdUJG6FdNiMJMQDZRDE feature-enable success
Hope this helps others also.
Peter
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155346#4155346
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155346
16 years, 1 month
[JBoss jBPM] - Re: Using end-complete-process attribute of end-state
by nizzy
Hi
Interestingly in my debug, I see that node-entered is the required end state however execution of the process does not finish at this point!
|
| 10:47:20,613 [main] INFO ForkTest : Signaling: Waiting for a
| 10:47:20,613 [main] DEBUG ForkTest : inside signal(instance, childKey = a)
| 10:47:20,613 [main] DEBUG GraphElement : event 'before-signal' on 'State(wait for a)' for 'Token(/a)
| '
| 10:47:20,613 [main] DEBUG GraphElement : event 'node-leave' on 'State(wait for a)' for 'Token(/a)'
| 10:47:20,613 [main] DEBUG GraphElement : event 'transition' on 'Transition(148aa23)' for 'Token(/a)'
|
| 10:47:20,613 [main] DEBUG GraphElement : event 'node-enter' on 'Node(doThis2)' for 'Token(/a)'
| 10:47:20,613 [main] DEBUG GraphElement : executing action 'Action(a46701)'
| 10:47:20,613 [main] DEBUG DoThis2ActionHandler : Calling leaveNode("failure")
| 10:47:20,613 [main] DEBUG GraphElement : event 'node-leave' on 'Node(doThis2)' for 'Token(/a)'
| 10:47:20,613 [main] DEBUG GraphElement : event 'transition' on 'Transition(failure)' for 'Token(/a)'
|
| 10:47:20,613 [main] DEBUG GraphElement : event 'node-enter' on 'EndState(end - doThis2 failed)' for
| 'Token(/a)'
| 10:47:20,613 [main] DEBUG GraphElement : event 'process-end' on 'ProcessDefinition(forktest)' for 'T
| oken(/)'
| 10:47:20,613 [main] DEBUG GraphElement : event 'after-signal' on 'State(wait for a)' for 'Token(/a)'
|
| 10:47:20,613 [main] INFO ForkTest : **************************************************
| 10:47:20,613 [main] INFO ForkTest : just performed action: 2. signal(instance, "wait for a")
| 10:47:20,613 [main] INFO ForkTest : root token node: Fork(fork1)
| 10:47:20,613 [main] INFO ForkTest : root token active children: {}
| 10:47:20,613 [main] INFO ForkTest : **************************************************
|
I also have noticed that ProcessInstance.hasEnded() is true, but I can still signal the process!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155336#4155336
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155336
16 years, 1 month
[JBoss jBPM] - Using end-complete-process attribute of end-state
by nizzy
Hi,
I have attached the update schema to the jira issue created by Tom.
This fixed the exception I was seeing. However I'm still not seeing the behaviour from the process execution that I would expect.
Could someone have a look at my test process definition and see if I'm doing something wrong
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="" name="forktest">
|
|
| <start-state name="start">
| <transition to="doThis1"></transition>
| </start-state>
|
|
| <node name="doThis1">
| <transition to="fork1"></transition>
| </node>
|
| <fork name="fork1">
| <transition to="wait for a" name="a"></transition>
| <transition to="wait for b" name="b"></transition>
| </fork>
|
| <node name="doThis2">
| <action class="com.ecebs.sample.action.DoThis2ActionHandler"></action>
| <transition to="join1" name="success"></transition>
| <transition to="end - doThis2 failed" name="failure"></transition>
| </node>
|
| <node name="doThis3">
| <action class="com.ecebs.sample.action.DoThis2ActionHandler"></action>
| <transition to="join1" name="success"></transition>
| <transition to="end - doThis3 failed" name="failure"></transition>
| </node>
|
| <join name="join1">
| <transition to="wait state"></transition>
| </join>
|
| <state name="wait for a">
| <transition to="doThis2"></transition>
| </state>
|
| <state name="wait for b">
| <transition to="doThis3"></transition>
| </state>
|
| <state name="wait state">
| <transition to="end"></transition>
| </state>
|
|
| <end-state name="end" />
| <end-state name="end - doThis2 failed" end-complete-process='true'/>
| <end-state name="end - doThis3 failed" end-complete-process='true'/>
|
|
| </process-definition>
I set in the ContextInstance a variable that I use to define success or failure, i.e. if success then I call
ctx.leaveNode("success")
from my action handler, if it fails then I calll same method passing in failure.
I still dont see the process completing at the expected end-state which leads me to believe I'm doing something wrong, either in my process definition or my test code
test code is
@Test
| public void testFork() {
| if (log.isDebugEnabled()) {
| log.debug("inside testFork()");
| }
|
| // Create an instance of the process definition.
| ProcessInstance instance = new ProcessInstance(processDefinition);
| debugState("new ProcessInstance()", instance);
| log.debug("ProcessId is " + instance.getId());
|
| // Signal to Start Process
| log.info("Signaling: Start");
| signal(instance, null);
| debugState("1. Start", instance);
|
| ContextInstance ctxInst = instance.getContextInstance();
| ctxInst.setVariable("status", "failure");
|
| // Signal: Waiting for a
| log.info("Signaling: Waiting for a");
| signal(instance, "a");
| debugState("2. signal(instance, \"wait for a\")", instance);
|
| ctxInst.setVariable("status", "success");
|
| // Signal: Waiting for a
| log.info("Signaling: Waiting for b");
| signal(instance, "b");
| debugState("3. signal(instance, \"wait for b\")", instance);
|
| // Signal: Waiting for a
| log.info("Signaling: to exit wait");
| signal(instance, null);
| debugState("3. signal(instance, \"null\")", instance);
|
| Assert.assertEquals(processDefinition.getNode("end - doThis2 failed"), instance.getRootToken().getNode());
| //Assert.assertEquals(processDefinition.getNode("end"), instance.getRootToken().getNode());
| }
|
| private void debugState(String action, ProcessInstance instance) {
| log.info("**************************************************");
| log.info("just performed action: " + action);
| log.info("root token node: " + instance.getRootToken().getNode());
| log.info("root token active children: "
| + instance.getRootToken().getActiveChildren());
| log.info("**************************************************");
| }
|
| private void signal(ProcessInstance instance, String childKey) {
| if (log.isDebugEnabled()) {
| log.debug("inside signal(instance, childKey = " + childKey + ")");
| }
|
| Token rootToken = instance.getRootToken();
| if (rootToken.hasActiveChildren()) {
| Map<?, ?> children = rootToken.getActiveChildren();
| if (children.containsKey(childKey)) {
| Token childToken = (Token) children.get(childKey);
| childToken.signal();
| } else {
| // TODO handle this
| String msg = "Root Token does not contain, " + childKey;
| log.debug(msg);
| throw new RuntimeException(msg);
| }
| } else {
| rootToken.signal();
| }
| }
Help is much appreciated!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155335#4155335
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155335
16 years, 1 month
[JBoss jBPM] - Re: Jbpm - EJB LazyInitialization Exception
by sreepathia＠gmail.com
Hi,
I understand your problem, This is because your transaction/session is initiated in EJB and it was completed automatically when you exited the EJB method. when you call processInstance.signal() JBPM will try to use the session associated with the processInstanceobject for updatign the database. which is closed in this scenario, There are couple of ways to do this
1) Try to complete all the database activities in one single method of EJB.
2) If you want to do this in multiple methods/layers then you need to make these both methods in one transaction like, start a transaction before calling the EJB object and end the transaction in your servelet or calling class after completing the process.
Spring has certain API to support thsi functionality,i implemented this in spiring but i am not sure how you will do it in EJB.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155323#4155323
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155323
16 years, 1 month