Official jBPM Support (Enterprise Framework Subscription) is for 3.2.8 and is
certified on RHELv4 and RHELv5.
Our jBPM certifications map to our SOA Platform certifications:
http://www.jboss.com/products/platforms/soa/testedconfigurations/
You can get an eval copy of SOA Platform from jboss.com
Hello jBPM Users, I'd like your thoughts on the following demonstration. It
uses jBPM to support service orchestration as well as human task management.
http://www.redhat.com/v/webcast/SOAdemo2/SOADemo2.html
Does the presented use case/scenario capture the value that jBPM brings to a
custom
Hello jBPM'ers,
This is a great blog by Kurt Stam on the ESB Core team that describes the
benefits of using jBPM to have a single end-to-end process flow that
incorporates both service orchestration and human-task management.
http://jbossesb.blogspot.com/2008/01/service-orchestration-using-jbpm.h
This not specifically a web service for command API of jBPM but...
the JBoss ESB has implemented core jBPM 3.2.x which means you can expose jBPM
APIs (deploy, create/start, signal, update vars) as JBoss ESB Services. JBoss
ESB Services can be exposed to the outside world as JMS, FTP, File drop,
Please consider taking this and putting together a wiki page along with the
appropriate screenshots. It would make an awesome contribution to the project.
Burr
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085217#4085217
Reply to the post :
http://www.jbo
If you download 4.2 then ESB & jBPM are "pre-integrated". There are 3 examples
that illustrate different ways to use the 2 togethe.
quickstarts:
jbpm_simple1
bpm_orchestration1
bpm_orchestration2
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079021#4079021
No, I was trying to indicate how a BPEL engine could be integrated with an ESB.
The ESB produces WS endpoints, the BPEL consumes them and vice versa. BPEL
only deals with WS endpoints. An ESB can handle things like JMS, FTP, native
connectors to legacy systems as well as WS.
View the origina
So if we put the jPDL+BPEL discussion aside and focus only on BPEL then that
engine if deployed in its own server instance should be able to operate with
the ESB deployed its own server (ESB Server or App Server) instance.
However, if you wish to run jBPM BPEL AND ESB in the SAME server instance
One of the things that you'll need to explore is if jBPM BPEL can be deployed
with jBPM JPDL in the same environment.
That might be your related to problem. The ESB 4.2 bundles in jBPM JPDL 3.2.1
already which makes for a very, very nice simple orchestration solution where
the service endpo
Run the build on it.
Worked for me.
Burr
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070322#4070322
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070322
___
jboss-user
I believe jPDL-based jBPM and BPEL-based jBPM can NOT run on the same server at
this moment.
Our team was working to correct that (and may have, my information could be
old).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067363#4067363
Reply to the post :
If you don't wish to "build from source", I would suggest another trick (though
untested). If you follow all the various steps outlined in this thread you'll
note that I believe the problem is finally with gravel14.jar. If you go to
jboss.org you can download gravel by itself and replace grave
Once you discover the "trick" in WLS, please make sure to build a wiki page
here that describes the deployment steps.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063488#4063488
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mod
Sounds like you wish to use a fork & join.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063486#4063486
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063486
___
jboss-user
How do you define "stable"? If your testing has shown that it supports your
use cases, your environmental conditions and handles your load then it is
stable from your perspective.
Would you mind providing some details (forums or email) about your expectations?
Thanks,
Burr
View the original
I decided to "cheat" and went back to CVS. The build script for the console
makes a 4.2 compatible WAR where the primary differences seem to the following:
jsf-impl-14.jar (gone)
jsf-api-14.jar (gone)
el-ri.jar (gone)
el-api.jar (gone)
javassist.jar (gone)
gravel-14.jar is now gravel.jar
So, th
I'll try to clearly specify my steps for the next person who will wish to
attempt this trick. My ultimate goal is to make the console with with the jBPM
embedded in the ESB 4.2 but for now I'm just shooting for AS 4.2.
- Plain vanilla AS 4.2 instance (no Messaging, no ESB, etc)
- jBPM 3.2.1 jPDL
Downloaded the "jbpm-jpdl-suite-3.2.1" - run the server and the console from
the bundled version of AS. No problem there.
Reviewed the information at this link:
http://wiki.jboss.org/wiki/Wiki.jsp?page=DeployJbpm3.2WebAppUnderJBoss4.2.x
Dropped the modified WAR (tried zipped and unzipped) into m
The partnership is more specifically between the JBoss ESB and Active
Endpoints. It is unrelated to jBPM's BPEL subproject which will continue on.
If you are interested being a contributor to jBPM's BPEL subproject please
raise your hand as there is plenty of things to do! :-)
The JBoss ESB al
Answering my own question about the cache issue.
This in my hibernate.cfg.xml helped out:
org.hibernate.cache.HashtableCacheProvider
So simply the removal of Dom4j from the web-inf/lib and adding ehcache1.2 to my
EAR seemed to sort this out.
If anyone else is interested in making jBPM
I'm attempting to get a jBPM.war based on 3.1.2 working on 4.0.5.GA. I also
found that DOM4J and Jaxen now ship with the AS 4.0.5.GA so I removed them from
the WEB-INF\lib so that helps.
However, I'm still stuck on
Could not instantiate cache implementation
The WAR is to simply allow for uploa
Can you deploy any 181 WS? Or is it just this one that is giving you troubles?
The portal may not necessarily have the EJB3 profile installed. In your deploy
directory look for "ejb3.deployer" and "jbossws.sar". The older WS stack had
phrases like "axis" and "ws4ee" sprinkled around and that
Check out:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWS181HelloWorld
And let me know what you think.
Burr
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960566#3960566
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3
23 matches
Mail list logo
