| Summary: | Investigate re-working SOA-P embedded server directory structure so we can "drop-in" EAP updates | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Tooling | Assignee: | trev <tkirby> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 CP01 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 CP04 ER1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-521 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-02-09 02:00:27 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Len DiMaggio
2008-04-22 20:24:24 UTC
It's more than a "drop-in". There is QE effort. There is also ESB integration that must occur too. And - doc concerns too (from Josh): This is an issue with the docs also. As Jay pointed out in SOA-508 [1], because the EAP docs are placed into a different directory location in the SOA-P, references to docs locations in the EAP docs are then wrong. Additionally the EAP Getting Started Guide section that maps the directory structure of the EAP component is also broken when the EAP is embedded in SOA-P. Other than Docs I'm not sure what you are wanting? jbpm-jpdl at the top level is nothing to do with EAP, it's there because JBDS wanted somewhere they could get at all the jbpm jars. Docs were moved to their current location as a result of a request from josh in https://jira.jboss.org/jira/browse/SOA-361 Can we move wholesale directories around in a CP? Link: Added: This issue is related to SOA-361 Link: Added: This issue is related to SOA-1300 SOA-1300 and the RPMs are a better place to track this. |