Bug 780053 (SOA-2418) - Change modeshape deployment to copy the correct modeshape-config.xml file based on the environment (i.e, SOA vs BRMS)
Summary: Change modeshape deployment to copy the correct modeshape-config.xml file bas...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2418
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Build Process, Configuration, Deployment, EDS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER3
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-13 15:26 UTC by Van Halbert
Modified: 2011-07-18 19:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-18 19:52:52 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2418 0 None None None Never

Description Van Halbert 2010-10-13 15:26:59 UTC
project_key: SOA

In order for modeshape to support both SOA and BRMS out-of-the-box, separate workspaces need to be defined in separate modeshape-config.xml files.   The correct config file will be deployed based on the enviornment.

Also, the web.xml in each deployment will need to be updated with corresponding default workspaces.

Comment 1 Van Halbert 2010-10-13 21:00:33 UTC
changed to use one config file, and then perform a property substitution at installation time based on the environment.

Comment 2 Van Halbert 2010-10-14 15:27:34 UTC
The modeshape-config.xml file will be dynamically updated during installation based installed environment (i.e, brms vs soa-p).   This includes setting the workspace and jboss home location.  If installed location is:   jboss-as-web   then workspace will be "brms"         if installed location is: jboss-as then workspace will be "eds".

Comment 3 Van Halbert 2011-07-18 19:52:52 UTC
Completed and verified for BRMS and SOA


Note You need to log in before you can comment on or make changes to this bug.