[JBoss jBPM] - Re: Need help to fix timer issue
by gchanteb
And it works with action handler:
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="process6">
|
| <start-state name="start-state1">
| <transition to="tsmactoncr"></transition>
| </start-state>
|
| <state name="tsmactoncr" async="true">
| <timer name="timer" duedate="7 seconds" transition="to escalated">
| <action class="yourpackage.Action1"></action>
| </timer>
| <transition to="normailflow" name="to normal flow"></transition>
| <transition to="escalationflow" name="to escalated"></transition>
| </state>
|
| <state name="normailflow">
| <event type="node-enter">
| <script>
| System.out.println("Node-enter: normailflow");
| </script>
| </event>
| <transition to="end-state1"></transition>
| </state>
|
| <state name="escalationflow">
| <event type="node-enter">
| <script>
| System.out.println("Node-enter: escalationflow");
| </script>
| </event>
| <transition to="end-state1"></transition>
| </state>
|
| <end-state name="end-state1"></end-state>
|
| </process-definition>
package yourpackage;
|
| import org.jbpm.graph.def.ActionHandler;
| import org.jbpm.graph.exe.ExecutionContext;
|
| public class Action1 implements ActionHandler
| {
| private static final long serialVersionUID = 532619789299259672L;
|
| @Override
| public void execute(ExecutionContext executionContext) throws Exception
| {
| for(int cpt=0;cpt<1000;cpt++)
| {
| System.out.println("Action 1: "+cpt);
| }
| }
| }
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218685#4218685
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218685
17 years, 3 months
[JBoss jBPM] - Re: Need help to fix timer issue
by gchanteb
It works:
<?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="process6">
|
| <start-state name="start-state1">
| <transition to="tsmactoncr"></transition>
| </start-state>
|
| <state name="tsmactoncr" async="true">
| <timer name="timer" duedate="7 seconds" transition="to escalated">
| <script>
| System.out.println("escalatedr---::"+node.getName());
| </script>
| </timer>
| <transition to="normailflow" name="to normal flow"></transition>
| <transition to="escalationflow" name="to escalated"></transition>
| </state>
|
| <state name="normailflow">
| <event type="node-enter">
| <script>
| System.out.println("Node-enter: normailflow");
| </script>
| </event>
| <transition to="end-state1"></transition>
| </state>
|
| <state name="escalationflow">
| <event type="node-enter">
| <script>
| System.out.println("Node-enter: escalationflow");
| </script>
| </event>
| <transition to="end-state1"></transition>
| </state>
|
| <end-state name="end-state1"></end-state>
|
| </process-definition>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218680#4218680
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218680
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - Re: Failed deployment, several tomcat deployment and ctxPath
by vaguardia
Thanks.
How you can see below there was a folder called sipre in the deploy folder.
| Directorio de C:\Tools\jboss-5.0.0.GA\server\default\deploy
|
| 17/03/2009 14:14 <DIR> .
| 17/03/2009 14:14 <DIR> ..
| 04/12/2008 17:23 2.065 cache-invalidation-service.xml
| 04/12/2008 17:23 372 ejb2-container-jboss-beans.xml
| 04/12/2008 17:23 2.911 ejb2-timer-service.xml
| 04/12/2008 17:23 1.506 ejb3-connectors-jboss-beans.xml
| 04/12/2008 17:23 423 ejb3-container-jboss-beans.xml
| 04/12/2008 17:23 27.783 ejb3-interceptors-aop.xml
| 04/12/2008 17:23 6.302 ejb3-timer-service.xml
| 04/12/2008 17:23 763 hdscanner-jboss-beans.xml
| 04/12/2008 17:23 5.211 hsqldb-ds.xml
| 04/12/2008 17:23 <DIR> http-invoker.sar
| 04/12/2008 17:23 14.394 jboss-local-jdbc.rar
| 04/12/2008 17:23 14.373 jboss-xa-jdbc.rar
| 04/12/2008 17:23 <DIR> jbossweb.sar
| 04/12/2008 17:23 <DIR> jbossws.sar
| 04/12/2008 17:23 2.536 jca-jboss-beans.xml
| 04/12/2008 17:23 81.347 jms-ra.rar
| 04/12/2008 17:23 <DIR> jmx-console.war
| 04/12/2008 17:23 6.052 jmx-invoker-service.xml
| 04/12/2008 17:23 <DIR> jmx-remoting.sar
| 04/12/2008 17:23 1.583 jsr88-service.xml
| 04/12/2008 17:23 2.565 legacy-invokers-service.xml
| 04/12/2008 17:23 14.791 mail-ra.rar
| 04/12/2008 17:23 1.722 mail-service.xml
| 04/12/2008 17:23 <DIR> management
| 04/12/2008 17:23 <DIR> messaging
| 04/12/2008 17:23 5.426 monitoring-service.xml
| 04/12/2008 17:23 7.703 profileservice-jboss-beans.xml
| 04/12/2008 17:23 1.847 properties-service.xml
| 04/12/2008 17:23 8.415 quartz-ra.rar
| 04/12/2008 17:23 8.287 remoting-jboss-beans.xml
| 04/12/2008 17:23 <DIR> ROOT.war
| 04/12/2008 17:23 4.941 schedule-manager-service.xml
| 04/12/2008 17:23 2.889 scheduler-service.xml
| 04/12/2008 17:23 <DIR> security
| 17/03/2009 14:12 <DIR> sipre
| 17/03/2009 13:31 52.002.219 sipre.war
| 04/12/2008 17:23 198 sqlexception-service.xml
| 04/12/2008 17:23 3.094 transaction-jboss-beans.xml
| 04/12/2008 17:23 2.872 transaction-service.xml
| 04/12/2008 17:23 <DIR> uuid-key-generator.sar
| 04/12/2008 17:23 425 vfs-jboss-beans.xml
| 30 archivos 52.235.015 bytes
| 13 dirs 43.003.359.232 bytes libres
|
When I removed it I could do the deployment successfully.
Thanks again.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218669#4218669
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218669
17 years, 3 months
[EJB 3.0] - Access the EJB2 bean from EJB3 Service problem
by konstantin.ermakov
Hi!
I am writing a small EJB3 Service app, which should call the EJB2 app. The code looks like this:
|
| @Service(name="MyService")
| @Depends("jboss.management.local:J2EEApplication=EJB2App.ear,J2EEServer=Local,j2eeType=EJBModule,name=EJB2App.jar")
| class MyManagement implements ManagementI, RemoteI {
|
| public void start() throws Exception() {
|
| ...
|
| ServiceHome home = (ServiceHome) context.lookup("IamHere");
| ServiceImpl impl = home.create(ctx); // <--
|
| ...
|
| };
|
| };
|
|
|
As soon as I call "home.create" the jboss hangs. What I noticed, that If I will deploy my service after the JBoss start and EJB2 app will be completly deployed, everything works fine. It seems to me, that I have to wait for the "start" of EJB2 App and not for the "Deploy". Does somebody met the similar problem? Any ideas?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218659#4218659
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218659
17 years, 3 months