[jBPM Users] - [jBPM4] Programatic deployment - DEPLOYPROP table is empty
by DrBrain
Hello,
I'm trying to programmatically deploy a process definition, using:
NewDeployment newDeployment = processEngine.getRepositoryService().createDeployment();
| newDeployment.addResourceFromString(processName, processDefinition).deploy();
The above creates two entires in my db, in JBPM4_DEPLOYMENT and JBPM4_LOB tables (nothing else is created in any other table).
Later on, when I try to start an instance of the above process like:
ExecutionService executionService = processEngine.getExecutionService();
| ProcessInstance pi = executionService.startProcessInstanceById(processID);
passing as 'processID' the value I obtained during deployment, I get:
org.jbpm.api.JbpmException: no process definition with id '15'.
(15 is my processID obtained during deployment).
Checking hibernate's queries, I see that jBPM is trying to execute:
select * from ( select deployment0_.DBID_ as DBID1_81_, deployment0_.DEPLOYMENT_ as DEPLOYMENT2_81_, deployment0_.OBJNAME_ as OBJNAME3_81_, deploym
| ent0_.KEY_ as KEY4_81_, deployment0_.STRINGVAL_ as STRINGVAL5_81_, deployment0_.LONGVAL_ as LONGVAL6_81_ from JBPM4_DEPLOYPROP deployment0_ where deployment0_.KEY_='pdid' and deployment0_.STRINGVAL_='
| 15' ) where rownum <= ?
The above query obviously fails as JBPM4_DEPLOYPROP is totally empty.
Any ideas what I may be doing wrong?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261197#4261197
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261197
16 years, 8 months
[jBPM Users] - timer not signalling to right transition
by freak182
Hello,
I have this process:
| <task-node name="Investigate">
| <task name="INV_LOAN">
| ..............
| </task>
| <timer duedate="1 minute" name="task_timer" transition="End Application">
|
| <action class="org.wicket.jbpm.engine.handlers.TimerAction"></action>
| </timer>
| <transition to="fork1" name="Loan Review"></transition>
| <transition to="End Loan Application" name="End Application"></transition>
| </task-node>
|
TimerAction is:
| public void execute(ExecutionContext context) throws Exception
| {
|
| jbpmEngine.endTimerTask(context);
| }
|
| @Override
| protected void initialiseHandler(BeanFactory factory)
| {
| jbpmEngine = (JbpmCoreEngine) factory.getBean("wf_core_engine");
| }
|
CoreEngine is:
| public void endTimerTask(ExecutionContext context)
| throws WicketJbpmException
| {
|
| try
| {
| final Collection<TaskInstance> tasks = context
| .getTaskMgmtInstance().getTaskInstances();
| for (TaskInstance tasksInts : tasks)
| {
|
| if (!tasksInts.hasEnded())
| {
| tasksInts.end();
| log.info("task name: " + tasksInts.getName() + " has ended.");
| }
| }
| // finally save the process instance contain here in timers
| context.getJbpmContext().save(
| context.getToken().getProcessInstance());
|
when the time is up it always take the: Loan Review transition.
am i missing something?
im using 3.3.1.GA
thanks a lot.
cheers.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261195#4261195
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261195
16 years, 8 months
[JBoss OSGi Users] - Re: JBossOSGi vs. Pax-Runner/Pax-Exam
by thomas.diesler@jboss.com
Alin Dreghiciu sais:
anonymous wrote :
| Regarding Pax Exam and Husky these two frameworks are almost the same. And both are working with an remote framework. Remote meaning that the Client Runner and Osgi Framework are running in separate processes. Now, of course that we do not share the same names like Conecor, invoker, bridge but architecture wise is the same. With one diff: we consider that all the tests have to run the osgi container and so we do not have the Bridge part in every test method. In rest, all the things like extender based on manifest headers, injection of bundle context, ...
| I would even say that Pax Exam adds more to the table because you can configure the osgi framework use for tests for things like system properties, boot delegation packages, system packages, provisioned bundles, ... IT may be that Husky supports that too but was not obvious from the blog post.
|
| After all, I do not really care if there are other test frameworks over there beside the split effort. As it looks like we think alike why don't you join us? Pax Exam provides an extension point where you can plug in another test container , beside pax runner based one. Implement that based on JBoss and just have it in the classpath and your pax exam tests will be running in JBoss.
|
| Actually the collaboration could be batter as we can work on adding support for JBoss in Pax Runner. This will mean that jboss can be easy started and used by pax runner users, directly used in Pax Exam without the need to implement the container explained above, could be used n Eclipse via Pax Runner plugin, ... WDYT?
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261192#4261192
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261192
16 years, 8 months