Hide Forgot
Date of First Response: 2007-11-29 18:58:59 project_key: SOA In looking at RHDS cr1 and SOA-P IR7, I found a situation that may cause some user confusion. In summary: In order for users who install RHDS and SOA-P to create new jBPM process projects, even projects based on the SOA-P bpm*_orchestration quickstarts, they will have to install jBPM 3.2.2 from jboss.org Here's the problem: In order to create a new jBPM process project in RHDS (or eclipse), a jBPM "runtime" needs to be defined in Preferences->jBPM-runtime. This runtime has to include the /src dir packaged under jBPM 3.2.2 - for example: --------------- [ldimaggi@ldimaggi src]$ pwd /opt/jbpm_Nov/jbpm-jpdl-3.2.2/src [ldimaggi@ldimaggi src]$ ll total 32 drwxr-xr-x 4 ldimaggi ldimaggi 4096 Sep 12 13:59 enterprise drwxr-xr-x 4 ldimaggi ldimaggi 4096 Sep 12 13:59 identity drwxr-xr-x 4 ldimaggi ldimaggi 4096 Sep 12 13:59 jpdl drwxr-xr-x 3 ldimaggi ldimaggi 4096 Sep 12 13:59 resources --------------- We do not currently package this in either SOA-P or RHDS. Users will have to download it separately. Note - that it is possible to create a new Java project, and import (file system import) the contents of a SOA-P bpm*_orchestration quickstart into that project and deploy it, but it won't be possible to compile the project. But - if a user creates a new (empty) jBPM process project, based on that same SOA-P bpm*_orchestration quickstart, the project creation cannot be completed without installing a jBPM runtime. So - do we want to require SOA-P users to download jBPM from jboss.org to compile jBPM process projects (and not include the runtime in SOA-P)? This seems broken - why not include it in SOA-P?
This sounds like a meeting agenda item. I don't have the answers to these questions.
Link: Added: This issue is related to GPD-192
FYI - not a surprise - the situation is the same in the just released: JBoss Developer Studio Build id: 200712091205-nightly
Still an open question - http://post-office.corp.redhat.com/mailman/private/soa-engineering-list/2007-December/msg00061.html
Link: Added: This issue is a dependency of SOA-235
Link: Added: This issue related JBDS-227
*How* is this going to be packaged ? I assume you will create a seperate root dir in the distro called jbpm or something similar (just so we don't have to repeat the saga over putting random framework dirs at random places inside jboss as were done about seam ;)
Max is right (again!). Just use the jbpm-jpdl.zip file, expand it as a root folder in the SOA distribution, and done.
well - I guess it needs to be a custom built as all the other parts of the platforms...but yes - using the plain distro sounds like the only right thing to do.
Yes. so at the top level in the distribution there will be the appserver root and a directory for each component that needs to include runtimes etc. appserver jbpm seam | | | bin, server etc. src etc. bits needed for seam
package target now adds contents of jbpm-jpdl.zip to top level of both versions.
i'm curious - what does "both versions" mean ? Isn't there just one SOA-P platform ?
no there are two, one embedded in EAP and one standalone.
ah ok. thanks for clarifying ;) Anywhere I could get a copy of these or info on the differences in file structure ? (This is to know how tooling should autodetect it)
The file structure is soa-4.2.0.beta1.zip - soa-4.2.0.beta1.zip - jboss-as - seam - jbpm-jpdl but should be soa-4.2.0.beta1.zip - soa-4.2.0.beta1.zip - jboss-as - seam - jbpm-jpdl Equivalent also for standalone
There is no as directory equivalent in the standalone so I've left the jbpm at the top level
i'm sorry, but that sounds like you put jbpm in the as directory !? ...that was *not* what should happen.
it's at the same level as seam. soa-4.2.0.beta2.zip - jboss-as - bin etc. - seam - jbpm-jpdl Standalone-soa-4.2.0.beta2.zip -standalone-soa-4.2.0.beta2 -bin etc - jbpm-jpdl
ok good...but I fail to see what your comment was about then ,)
Link: Added: This issue is related to SOA-334
Verified in beta2 build.
Link: Added: This issue related SOA-2332
Link: Added: This issue related SOA-2448