[jboss-dev-forums] [Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss

[kukeltje]

1. correct
2. only partly true. Let me elaborate
a) not to difficult, but the problem was that the identity scripts were separate. This has been fixed recently (in cvs and will be in 3.2.1)
b) Right, or use the GPD
c) depends on the jboss version. for 4.0.4.GA you can just deploy the jbpm-console war file and be up and running. The profiles in the build scripts should be adapted/expanded to cope with other versions. People expecting to deploy the war from the starterkit (4.0.4) in 4.2 have a problem because of jsf libs... I think addressing this is more important for JBoss

A real process deployer would be great. This has been discussed in the forums before. The thing is that you need a kind of versioning to check if a processarchive should be redeployed after starting or not. See the versioning issues in jira

Please allow me to address a separate issue. jBPM has its own identity module. To some extend it is similar to the one in the portal. People often do not get this login thing and that was the reason it was dropped from 3.0 compared to 2.0. In 3.2 (or was it 3.1) it was reintroduced, but lining up the portal usermanagement and the one from jBPM would be realy nice. Maybe the usermanagement part should be a separate project (combine it with the sso?). This   way both jBPM and portal can take separate advantage of it, but at the same time be compatible... 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051929#4051929

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051929