[Design of JBoss jBPM] - Problems building GWT-Console-JBPM
by alegomes
Hi,
I was trying to build gwt-console-jbpm as stated in [1] but some issues came up:
a) JBPM artifact version 3.3.0-SNAPSHOT could not be found in any repository. So, I changed it to 3.3.0.CR1.
<!-- By Ale! jbpm.version>3.3.0-SNAPSHOT</jbpm.version -->
| <jbpm.version>3.3.0.CR1</jbpm.version>
b) There is a compilation error:
[INFO] Compiling 25 source files to /Volumes/Data/Code/redhat/jbpm/gwt-console/server/target/classes
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD FAILURE
| [INFO] ------------------------------------------------------------------------
| [INFO] Compilation failure
|
| /Volumes/Data/Code/redhat/jbpm/gwt-console/server/src/main/java/org/jboss/bpm/console/server/dao/internal/JBPM3CommandDelegate.java:[109,26] cannot find symbol
| symbol : class DeleteProcessdefinitionCommand
| location: class org.jboss.bpm.console.server.dao.internal.JBPM3CommandDelegate
|
| /Volumes/Data/Code/redhat/jbpm/gwt-console/server/src/main/java/org/jboss/bpm/console/server/dao/internal/JBPM3CommandDelegate.java:[123,13] cannot find symbol
| symbol : method setProcessId(long)
| location: class org.jbpm.command.GetProcessInstancesCommand
|
[1] https://www.jboss.org/community/docs/DOC-12879
thanks
Alexandre Gomes
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187488#4187488
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187488
16 years, 2 months
[Design of JBoss jBPM] - Building the installer
by jbarrez
When I do an anonymous checkout from svn, I get this error:
(Thomas: could it be the same error you had Tuesday? If so, what is the solution?)
Missing:
| ----------
| 1) org.jbpm.jbpm3:jbpm-enterprise-beans:jar:sources:3.3.0-SNAPSHOT
|
| Try downloading the file manually from the project website.
|
| Then, install it using the command:
| mvn install:install-file -DgroupId=org.jbpm.jbpm3 -DartifactId=jbpm-enterprise-beans -Dversion=3.3.0-SNAPSHOT -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file
|
| Alternatively, if you host your own repository you can deploy the file there:
| mvn deploy:deploy-file -DgroupId=org.jbpm.jbpm3 -DartifactId=jbpm-enterprise-beans -Dversion=3.3.0-SNAPSHOT -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
|
| Path to dependency:
| 1) org.jbpm.jbpm3:jbpm-distribution:pom:3.3.0-SNAPSHOT
| 2) org.jbpm.jbpm3:jbpm-enterprise-beans:jar:sources:3.3.0-SNAPSHOT
|
| 2) org.jbpm.jbpm3:jbpm-identity:jar:sources:3.3.0-SNAPSHOT
|
| Try downloading the file manually from the project website.
|
| Then, install it using the command:
| mvn install:install-file -DgroupId=org.jbpm.jbpm3 -DartifactId=jbpm-identity -Dversion=3.3.0-SNAPSHOT -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file
|
| Alternatively, if you host your own repository you can deploy the file there:
| mvn deploy:deploy-file -DgroupId=org.jbpm.jbpm3 -DartifactId=jbpm-identity -Dversion=3.3.0-SNAPSHOT -Dclassifier=sources -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
|
| Path to dependency:
| 1) org.jbpm.jbpm3:jbpm-distribution:pom:3.3.0-SNAPSHOT
| 2) org.jbpm.jbpm3:jbpm-identity:jar:sources:3.3.0-SNAPSHOT
|
| ----------
| 2 required artifacts are missing.
|
| for artifact:
| org.jbpm.jbpm3:jbpm-distribution:pom:3.3.0-SNAPSHOT
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187468#4187468
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187468
16 years, 2 months
Suspend/resume
by Karel Vervaeke
I notice that when a processInstance is suspended and resumed, all tasks
that were previously ended are reopened.
In queries following the pInstance.resume(), tasks are returned that
should have been closed.
Cause: ProcessInstance.suspend/resume delegates to
TaskInstance.suspend/resume, which has the side-effect of setting isOpen
next to isSuspended:
public void suspend() {
isSuspended = true;
isOpen = false; <----- seems good, prevents queries from
returning tasks in suspended processes
}
public void resume() {
isSuspended = false;
isOpen = true; <----- not so good, reopens tasks that were
previously closed
}
Is this a bug or a feature?
Karel
16 years, 2 months
[Design of JBoss jBPM] - donating an ANT task to the jBPM project
by tom.baeyens＠jboss.com
on behalf of Jim:
"Jim" wrote : I've enhanced an existing ANT task called GenJar -- http://genjar.sourceforge.net/ that is LGPL licensed, and have received the OK from my boss to donate it back to the jBPM project. The original task walks the dependency tree of the classes of interest and builds the list of classes to put in a jar. I had modified the main class of the task and added another class so it will inspect the processdefinition.xml file being deployed and walk the dependency tree of all of the delegation classes that all of the handlers call out to.
|
| There are a few upsides:
| - Smaller deployment to the database
| - Deploy time checking of class names (I've deployed processes with wrong package / class name before, and it blows up at runtime -- this catches it at deploy time)
| - fairly easy to use
|
| One drawback:
| - Interface based programming isn't possible (I think this can be worked around with Spring Java Config)
|
|
| Please let me know how best to proceed so I can donate the code to the jBPM project.
|
| Thanks,
| Jim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187278#4187278
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187278
16 years, 2 months
Migration
by Tom Baeyens
Jeff, Burr, Martin,
Afaict, you are the guys closest to our customers. Next week, we'll be discussing
migration between jBPM 3 and 4 in the team. We would appreciate your input.
If we had unlimited resources, we'ld simply provide DB, process-XML and API backwards
compatibility, but given that our resources are limited and the improvements
numerous, here are my initial thoughts on how we currently think to handle migration:
Probably DB migration will be too hard to supply in a decent manner. So we'll
probably target that users will be able to use jBPM 3 and jBPM 4 in parralel. That
way they can start deploying new processes to jBPM 4 and let jBPM 3 processes fade out.
For each process in jBPM 3, they could migrate the process to jBPM 4 (see below),
redeploy and start new executions in jBPM 4. Although from the user client code
perspective this will be hard or impossible.
We also anticipate that we'll have to supply a process translation tool that can
translate jPDL 3 process XML files to jBPM 4 process XML files. Most of the process
file will be converted. But probably there will be some things in jBPM 3 that we
will not support in the exact same way in jBPM 4. So some converted processes might
not be complete or might not execute exactly the same way as in jBPM 3.
API will be different. Only migration docs. The good news is that with the arrival
of jBPM 4, we'll start to ship a more limited API that is more decoupled from the
engine internals so that it will remain much more stable from then onwards.
Feedback from our jBPM Community Day in Dublin was very clear: Migration is one of
the biggest concerns for our users.
So here are my questions:
What aspect of migration will be the biggest challenge for our customers ?
Which aspects of migration will be showstoppers for ourcustomers ?
Suppose that we ship the above migration strategy and a really really really
important client wants to migrate his DB really really really badly. Would we
a) be able to say no.
b) provide him with skeleton code that the client can use as a basis to write their
own DB migration in code.
c) let our consultants work out the DB migration for the first customer that wants to
pay for it and then add it to the jBPM codebase.
--
regards, tom.
16 years, 3 months
