Hide Forgot
Steps to Reproduce: 1) Download and unzip BRMS standalone 5.1.0 CR1 2) Go to modeshape directory and install modeshpe (run ant) 3) Go to jboss-as-web/server/{profile}/deploy and there are BRMS and EDS data sources. securitylevel_name: Public When modesape is installed into BRMS standalone the EDS data source (modeshape-eds-store-ds.xml) is deployed into deploy/ directory. Only BRMS data source should be deployed, because EDS data source is not used by BRMS. It is not affecting the modeshape's behaviour, but it is also not necessary to deploy it (in case of BRMS).
Just to make sure I'm clear on the usecase here for ModeShape. Its only to be used under brms. Therefore, the following should also be done: - the modeshape configuration needs to have the eds repository removed, that references the eds -ds.xml - the modeshape configuration should have all the sequencers removed, since the brms controls what .cnd's its adding. - if the usecase is only thru brms, then the modeshape examples should be removed because they're meant for exposing publishing/unpublishing via another method other than brms.
Release Notes Text: Added: Applied the changes to the build process and should be in the future ModeShape kit builds.
Labels: Added: rn-dlesage rn-open
Labels: Removed: rn-dlesage rn-open Added: rn-dlesage rn-not-needed
Release Notes Docs Status: Added: Not Required Writer: Added: dlesage
I agree with Van. Verified fixed in BRMS 5.1.0.GA with modeshape from SOA 5.1.0.ER6.