[JBoss JIRA] Created: (JBPM-2281) figure out dependecies for Element.setUserData
by Tom Baeyens (JIRA)
figure out dependecies for Element.setUserData
----------------------------------------------
Key: JBPM-2281
URL: https://jira.jboss.org/jira/browse/JBPM-2281
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0.CR1
Burr reported it while running the demo.setup script:
BUILD FAILED
C:\demo\jbpm-4.0.0.Beta2\jboss\build.xml:54: The following error occurred while
executing this line:
java.lang.AbstractMethodError: org.apache.xerces.dom.ElementNSImpl.setUserData(L
java/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Obje
ct;
And I have seen it before when running an example in the enterprise module classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBPM-2467) ForkActivity setActivity(null) breaks console integration (process state diagram and others)
by Marko Friedemann (JIRA)
ForkActivity setActivity(null) breaks console integration (process state diagram and others)
--------------------------------------------------------------------------------------------
Key: JBPM-2467
URL: https://jira.jboss.org/jira/browse/JBPM-2467
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console, GPD
Affects Versions: jBPM 4.0
Environment: Jboss 5.1.0 GA on Windows XP
Reporter: Marko Friedemann
When deploying processes with forks in them, attempting to start them or view their state in the GWT-console causes exceptions (see attachment).
Apparently, the console integration code gets upset about the activity of the parent execution being null.
The activity is set to null by:
,-- ForkActivity.java, lines 73-79 --
| if (Execution.STATE_ACTIVE_ROOT.equals(execution.getState())) {
| concurrentRoot = execution;
| execution.setState(Execution.STATE_INACTIVE_CONCURRENT_ROOT);
| execution.setActivity(null);
| } else if (Execution.STATE_ACTIVE_CONCURRENT.equals(execution.getState())) {
| concurrentRoot = execution.getParent();
| }
`----------------
Now, I admit of not having an idea about much of the inner working of the pvm/jpdl/console etc., but I do wonder why it would be necessary to set this to null when it is marked as inactive anyway?
After trying to workaround it in the console code (ModelAdaptor.java, around line 100 with a Todo linking to https://jira.jboss.org/jira/browse/JBPM-2220) I commented out the setActivity() part and have the process running nicely now. Maybe I will hit side-effects later on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBPM-2511) move tmp directory of signavio installation to install/generated
by Tom Baeyens (JIRA)
move tmp directory of signavio installation to install/generated
----------------------------------------------------------------
Key: JBPM-2511
URL: https://jira.jboss.org/jira/browse/JBPM-2511
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Joram Barrez
Fix For: jBPM 4.2
while installing signavio, this is logged
internal.set.signavio.repo.dir:
[mkdir] Created dir: c:\software\jbpm-4.1\signavio-repository
[mkdir] Created dir: c:\software\jbpm-4.1\temp-signavio-unzip
[unzip] Expanding: c:\software\jbpm-4.1\install\src\signavio\jbpmeditor.war into c:\software\jbpm-4.1\temp-signavio-unzip
[zip] Building zip: c:\software\jbpm-4.1\temp-signavio-unzip\jbpmeditor.war
the temporary location should become install/generated/signavio-tmp
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months