[Design of JBoss jBPM] - what's wrong with deployment
by bill.burke@jboss.com
Let me expand on why I don't like JBPM deployment model:
* First of all, if you are deploying via an ANT script or the designer, these mechanisms need a database and knowledge how to connect to it. This requires the user to either set up a database (MYSQL/Oracle), or use JBoss's embedded Hypersonic. The user then also has to configure
* I don't like the Servlet mode of configuration at all. WHy? Because its inconsistent with the way Seam deploys JBPM and inconsistent with they way every other JBoss project does deployment.
There is a huge problem at JBoss.org at the moment. Every project is more interested in being portable to other non-JBoss environments than taking advantage of the JBoss platform and becoming one, integrated consistent suite. Take deployment for instance: Seam does it different than JBPM which does it different than ESB which does it different than AppServer wich does it different than Drools. I brought ESB into the JBoss deployment model, I'd like to do the same for JBPM.
We need to start being consistent across JBoss.org projects. This way we can start writing generic tools and frameworks that can abstract things like deployment and write a portability layer to other application servers. JBoss 5 kernel does a lot to modularize things and the JBoss Embedded project is where I want to write this portability layer.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052146#4052146
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052146
18 years, 10 months
[Design of JBoss jBPM] - RAR
by bill.burke@jboss.com
"kukeltje" wrote : anonymous wrote : A RAR would be limited and you would still need to deploy 2 separate files, a pd-ds.xml file, to define the process instance, and the .par file (or .jpdl file). Where in a JBoss deployer, its just one file and less metadata to write.
|
| Not completely. It is not really a pd-ds.xml but a jbpm-ds.xml. Multiple processdefinitions can share the same jbpm database. In fact, if you have a separate ds for each process you also have to deploy the console app multiple times to connect to the different ds's.
You're missing my idea. A JBoss -ds.xml file really isn't solely a datasource definition, it is an outbound adapter definition/configuration. Each process definition would be a an instance/activation of the JBPM RAR resource adapter. Just like a datasource in JBoss is an activation of the JDBC RAR.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052138#4052138
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052138
18 years, 10 months