[jBPM] - Errata in jBPM User Guide
by Manuel Jordan
Manuel Jordan [http://community.jboss.org/people/dr_pompeii] created the discussion
"Errata in jBPM User Guide"
To view the discussion, visit: http://community.jboss.org/message/544401#544401
--------------------------------------------------------------
Dear Members
Reading and learning carefully from your +jBPM User Guide+ documentation
I think that I found some minimum errata
1)Section http://docs.jboss.com/jbpm/v4/userguide/html_single/#deployingaprocess 5.3. Deploying a process
Has its sentence
The assigned version will be one higher then the highest version number
of deployed process definitions with the same key.
I think that the bold part should be *than* and not +then+
2) Section http://docs.jboss.com/jbpm/v4/userguide/html_single/#taskservice 5.7. TaskService
has its code
long taskId = task.getId();
Set<String> variableNames = taskService.getVariableNames(taskId);
variables = taskService.getVariables(taskId, variableNames);
variables = new HashMap<String, Object>();
variables.put("category", "small");
variables.put("lires", 923874893);
taskService.setVariables(taskId, variables);
See that *variables* is used firstly to get some data but not used anymore
and then it is used to create a HashMap, is it an +error about logic+?
3) Below in the same section we have
If a task has one outgoing transition with a name then:
gtaskService.etOutcomes() returns a collection that includes only the name of the transition
it should be *t*askService.*g*etOutcomes()
4) In section *6.2.5.3. end multiple*
has its code
<process name="EndMultiple" xmlns="http://;jbpm.org/4/jpdl">
<start>
<transition to="get return code" />
<start>
<state name="get return code">
The bold tag is not closed, should be *+</+*start>
I not finish to read all the documentation yet, of course if I find more errata I will let you know
My Best Regards
-Manuel
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544401#544401]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months
[JBoss Tools] - Installing JBoss Tools on Eclipse 3.6 RC
by Karsten Wutzke
Karsten Wutzke [http://community.jboss.org/people/kwutzke] created the discussion
"Installing JBoss Tools on Eclipse 3.6 RC"
To view the discussion, visit: http://community.jboss.org/message/544397#544397
--------------------------------------------------------------
Hello all,
I'm new to JBoss and Hibernate. I have Eclipse 3.6 RC1 on my Windows 64 bit machine and I was trying to install JBoss Tools by using the Eclipse update tool as described at
https://www.jboss.org/tools/download/stable/3_1_GA.html https://www.jboss.org/tools/download/stable/3_1_GA.html
or rather
https://www.jboss.org/tools/download/installation/update_3_1.html https://www.jboss.org/tools/download/installation/update_3_1.html
However, because I have Eclipse 3.6 RC1 (Helios) I seem to get dependency problems all over. I'm using the update site URL from the first link above:
http://download.jboss.org/jbosstools/updates/JBossTools-3.1.0.GA
Here's what Eclipse says:
Cannot complete the install because of a conflicting dependency.
Software being installed: Seam Tools 3.1.0.v201003050540R-H56-GA (org.jboss.tools.seam.feature.feature.group 3.1.0.v201003050540R-H56-GA)
Software currently installed: Eclipse IDE for Java and Report Developers 1.3.0.20100517-1551 (epp.package.reporting 1.3.0.20100517-1551)
Only one of the following can be installed at once:
International Components for Unicode for Java (ICU4J) 4.2.1.v20100412 (com.ibm.icu 4.2.1.v20100412)
International Components for Unicode for Java (ICU4J) 4.0.1.v20090822 (com.ibm.icu 4.0.1.v20090822)
International Components for Unicode for Java (ICU4J) 4.0.1.v20090415 (com.ibm.icu 4.0.1.v20090415)
Only one of the following can be installed at once:
Common Frameworks 1.2.0.v201003040800 (org.eclipse.wst.common.frameworks 1.2.0.v201003040800)
Common Frameworks 1.1.300.v200904160730 (org.eclipse.wst.common.frameworks 1.1.300.v200904160730)
Cannot satisfy dependency:
From: Eclipse IDE for Java and Report Developers 1.3.0.20100517-1551 (epp.package.reporting 1.3.0.20100517-1551)
To: org.eclipse.epp.package.reporting.feature.feature.group [1.3.0.20100517-1551]
Cannot satisfy dependency:
From: EPP Reporting Feature 1.3.0.20100517-1551 (org.eclipse.epp.package.reporting.feature.feature.group 1.3.0.20100517-1551)
To: org.eclipse.platform.feature.group [3.6.0.v20100512-9gF78GpqFsgprEYh7z-Q7acirDtvcwz-ebYa]
Cannot satisfy dependency:
From: Dali Java Persistence Tools - Core 2.2.1.v200908270220 (org.eclipse.jpt.core 2.2.1.v200908270220)
To: bundle org.eclipse.jst.j2ee [1.1.200,1.2.0)
Cannot satisfy dependency:
From: Dali Java Persistence Tools - Core 2.2.1.v200908270220 (org.eclipse.jpt.core 2.2.1.v200908270220)
To: bundle org.eclipse.wst.common.frameworks [1.1.200,1.2.0)
Cannot satisfy dependency:
From: Java EE Component 1.1.301.v200909030330 (org.eclipse.jst.j2ee 1.1.301.v200909030330)
To: bundle com.ibm.icu [3.4.4,4.1.0)
Cannot satisfy dependency:
From: Java EE Component 1.1.301.v201001272230 (org.eclipse.jst.j2ee 1.1.301.v201001272230)
To: bundle com.ibm.icu [3.4.4,4.1.0)
Cannot satisfy dependency:
From: Java EE Component 1.1.400.v201004292000 (org.eclipse.jst.j2ee 1.1.400.v201004292000)
To: bundle org.eclipse.wst.common.frameworks [1.2.0,2.0.0)
Cannot satisfy dependency:
From: Java EE Component 1.1.400.v201005130500 (org.eclipse.jst.j2ee 1.1.400.v201005130500)
To: bundle org.eclipse.wst.common.frameworks [1.2.0,2.0.0)
Cannot satisfy dependency:
From: Eclipse Platform 3.6.0.v20100512-9gF78GpqFsgprEYh7z-Q7acirDtvcwz-ebYa (org.eclipse.platform.feature.group 3.6.0.v20100512-9gF78GpqFsgprEYh7z-Q7acirDtvcwz-ebYa)
To: org.eclipse.rcp.feature.group [3.6.0.v20100427-9KAjFKvFs-Uz-4QX1m0EdXVS]
Cannot satisfy dependency:
From: Eclipse RCP 3.6.0.v20100427-9KAjFKvFs-Uz-4QX1m0EdXVS (org.eclipse.rcp.feature.group 3.6.0.v20100427-9KAjFKvFs-Uz-4QX1m0EdXVS)
To: com.ibm.icu [4.2.1.v20100412]
Cannot satisfy dependency:
From: Hibernate Tools 3.3.0.v201003050540R-H56-GA (org.hibernate.eclipse.feature.feature.group 3.3.0.v201003050540R-H56-GA)
To: org.jboss.tools.hibernate.jpt.core [3.3.0.v201003050540R-H56-GA]
Cannot satisfy dependency:
From: Hibernate Jdt Core 3.3.0.v201003050540R-H56-GA (org.jboss.tools.hibernate.jpt.core 3.3.0.v201003050540R-H56-GA)
To: bundle org.eclipse.jpt.core [2.2.0,2.2.2)
Cannot satisfy dependency:
From: Seam Tools 3.1.0.v201003050540R-H56-GA (org.jboss.tools.seam.feature.feature.group 3.1.0.v201003050540R-H56-GA)
To: org.hibernate.eclipse.feature.feature.group 3.2.0
Hmmm... I did not expect JBoss Tools not to work with a newer Eclipse version. The errors above are not like they make a lot of sense to me. Does anyone know what they mean in human language (preferrably English)?
Is there any cure for this (other than installing Eclipse 3.5, which is not desired)?
Karsten
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544397#544397]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months
Re: [jboss-user] [jBPM Development] - JBPM-2414 and JBPM-2506
by Maciej Swiderski
Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion
"JBPM-2414 and JBPM-2506"
To view the discussion, visit: http://community.jboss.org/message/544387#544387
--------------------------------------------------------------
Hi,
as suggested, I started to look into multiplicity attribute of join activity and found out that there is quite serious issue (if I got it right).
In general, please consider following scenario:
- there is a process with one fork that has three branches
- each of the branch points to another task activity
- join activity uses multiplicity attribute to continue flow as soon as two any branches will reach it
- after join there is a state activity
So what will happen is that after two tasks will be completed execution will move on to state activity but the last task will still be active. So in case where some one would like to signal the execution (assuming that execution is now in state node) there will be an exception (execution[ForkJoingMultiplicity.7] is not active: inactive-concurrent-root) because signalling will be task instead of state activity.
In my opinion (in case of using multiplicity attribute of join) all not finished child execution should be terminated at the time of signaling join activity to prevent problems with active executions.
Hope I described the issue good enough.
Please find attached test case that should fail when using trunk version of join activity together with multiplicity attribute.
I made a fix for it but just want to discuss that my understanding is correct.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/544387#544387]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 11 months