[jBPM] - The many WorkItemHandler
by Ramiro Pereira de Magalhães
Ramiro Pereira de Magalhães [https://community.jboss.org/people/ramiro] created the discussion
"The many WorkItemHandler"
To view the discussion, visit: https://community.jboss.org/message/733087#733087
--------------------------------------------------------------
Hello guys,
We're writing an application with jBPM 5.2 which setup is very similar to the one described by Gergely Dombi in https://community.jboss.org/message/588852#588852#588852 https://community.jboss.org/message/588852#588852. The big difference is that, due to several rules, we must package the whole application in a WAR file and we cannot control threads or install new "servers", such as MinaTaskServer. But we can use every resource available in a JEE server, such as JMS, JTA, EJB, etc.
Question is: does anyone know documentation or instructions to sobre setup an application with jBPM 5.2 in of cases such as mine? Also, I did notice you have many different implementations of WorkItemHandler, but those classes are not documented and I'm not finding mutch information on the web. Does anyone know a reference to some documentation about those classes?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/733087#733087]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 3 months
[jBPM] - How to build/modify jbpm-console and deploy it on server.
by Adam Bach
Adam Bach [https://community.jboss.org/people/heathcliff] created the document:
"How to build/modify jbpm-console and deploy it on server."
To view the document, visit: https://community.jboss.org/docs/DOC-18178
--------------------------------------------------------------
Info gathered from IRC discussion with tsurdilo:
1) install git and maven
2) git clone https://github.com/bpmc/bpm-console.git https://github.com/bpmc/bpm-console.git
3) mvn clean install -Dconsole.profile=jbpm -Dfull -DskipTests
4) mvn eclipse:eclipse
5) git clone https://github.com/droolsjbpm/jbpm.git https://github.com/droolsjbpm/jbpm.git
6) mvn clean install -Dfull -DskipTests
7) open eclipse, import projects.
8) search pom files in jbpm for "<version>2.3.4.Final</version>" and replace with "<version>2.4.0-SNAPSHOT</version>". This tells to use local version
9) change bpm-console code -> compile console code -> compile jbpm code
10)after that go to your $jbpm/jbpm-distribution/target dir
there you will find the distro zips you just built
11) copy jbpm-5.3.0-SNAPSHOT-bin.zip and jbpm-5.3.0-SNAPSHOT-gwt-console.zip from $jbpm/jbpm-distribution/target dir
to $installer-dir$/lib directory
12) now your installer (if you have 5.2 is not going to use jbpm 5.3.0..itll be on 5.2.0
so in this step edit $installer-dir$/build.properties and make sure you update your jbpm version to jBPM.version=5.3.0-SNAPSHOT
Also you need to add to $install-dir$\db\persistence.xml following entities
<class>org.jbpm.process.audit.ProcessInstanceLog</class>
<class>org.jbpm.process.audit.NodeInstanceLog</class>
<class>org.jbpm.process.audit.VariableInstanceLog</class>
6) in $installer-dir$ run:
ant clean.demo
ant install.demo (or ant install.demo.noeclipse if you dont want eclipse)
ant start.demo (or ant start.demo.noeclipse if you dont want eclipse)
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-18178]
Create a new document in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
14 years, 3 months
Re: [jboss-user] [JBoss Tools] - JBoss Source Lookup
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] commented on
"JBoss Source Lookup"
To view all comments on this blog post, visit: https://community.jboss.org/community/tools/blog/2012/01/24/jboss-source-...
--------------------------------------------------
about #3 then AS7.x runtime does not include the implementations currently - just the necessary for actually compiling.
Mainly to avoid collision at runtime (i.e. junit tests etc.)
With the source lookup feature in place and m2e-wtp automatically removing this classpath we might be better of actually including the runtime but then comes the problem you just witnessed: multiple versions of the same jar...feels like we can't find a way that will work well in most cases..
--------------------------------------------------
14 years, 3 months