| Summary: | We need to add jBPM runtime to SOA-P to support creating/compiling jBPM process projects | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | JBPM - within SOA, Build Process | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 Beta 1 | CC: | max.andersen |
| Target Milestone: | --- | ||
| Target Release: | 4.2 Beta 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-191 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-21 14:56:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 777719 | ||
|
Description
Len DiMaggio
2007-11-29 20:06:03 UTC
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 |