Bug 780967 (SOA-3438) - Enterprise Data Service (EDS) ant installer fails - missing modeshape-config-brms.xml
Summary: Enterprise Data Service (EDS) ant installer fails - missing modeshape-config-...
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-3438
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-04 16:40 UTC by Michael Pellegrini
Modified: 2011-11-15 17:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-15 17:49:48 UTC
Type: Bug


Attachments (Terms of Use)


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

Description Michael Pellegrini 2011-10-04 16:40:33 UTC
Steps to Reproduce: Install the deployable version of BRMS 5.2 war to SOA-P default server location and then run ant installer for EDS.
Workaround Description: Remove jboss-brms.war folder from default location before running EDS installer.  Or comment out appropriate XML to disable copy.
project_key: SOA

When running the ant installer for EDS I receive the following error

BUILD FAILED
/home/Michael/Applications/jboss-soa-p-5/eds/build.xml:52: The following error occurred while executing this line:
/home/Michael/Applications/jboss-soa-p-5/eds/build.xml:126: The following error occurred while executing this line:
/home/Michael/Applications/jboss-soa-p-5/eds/modeshape/build.xml:220: Warning: Could not find file /home/Michael/Applications/jboss-soa-p-5/eds/modeshape/resources/modeshape-config-brms.xml to copy.

This is due to the missing modeshape-config-brms.xml.  In my configuration I have the jboss-brms.war deployed to my SOA-P default server.

If the EDS ant build.xml detects that the brms war is installed, it tries to then copy this file which does not exist.

Comment 1 Van Halbert 2011-10-04 16:51:39 UTC
This is because the EDS modeshape installation wasn't configured to work with brms in SOA, because the configuration is different when modeshape is in SOA versus the BRMS kit.   The work around is to install EDS first, then deploy your brms war.   But modeshape won't be configured to work with brms in SOA.

Comment 2 Michael Pellegrini 2011-10-04 16:59:57 UTC
Seeing that eds/modeshape/resources/modeshape-config-brms.xml does not exists in the first place when would this install ever work?  Seems to me something else is not quite right.

Also, is the install order documented anywhere?  I was not able to find anything in my searching.

Comment 3 Van Halbert 2011-10-04 17:04:29 UTC
This works when modeshape is deployed in the brms kit.   This was never an option in SOA and never tested to this point.

Comment 4 Van Halbert 2011-10-04 17:05:32 UTC
The brms kit (brms-standalone-5.3.0.zip) comes with modeshape and can be deployed.


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