Description of problem: Follow the steps in quickstarts/overlord/sramp/s-ramp-demos-switchyard - the project cannot be built because of the switchyard error. It's possible it is caused by this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1043425 Version-Release number of selected component (if applicable): 6.0.0.ER7-2 How reproducible: 100% Steps to Reproduce: 1. follow the steps in quickstart readme 2. execute mvn -Pdemo clean deploy Actual results: Expected results: Additional info: Failed to execute goal org.switchyard:switchyard-plugin:1.1.1-p2-redhat-1:configure (default) on project s-ramp-demos-switchyard: SWITCHYARD011602: Model [org.switchyard.config.model.switchyard.v1.V1SwitchYardModel] is invalid: cvc-complex-type.4: Attribute 'targetNamespace' must appear on element 'composite'. -> [Help 1]
*** This bug has been marked as a duplicate of bug 1041334 ***
Present in ER8
Do you have any steps to reproduce this? I downloaded and installed ER8 - I also downloaded the repository. However, when I try to run the demo I get all sorts of errors. I can run this demo from the community tree OK.
Hi Eric! steps you are asking for: 1. install FSW 6.0.0.ER8 (& configure ER8 maven repo) 2. cd to quickstarts/overlord/sramp/s-ramp-demos-switchyard 3. run mvn clean package -P demo result: [ERROR] Failed to execute goal org.switchyard:switchyard-plugin:1.1.1-p2-redhat-2:configure (default) on project s-ramp-demos-switchyard: SWITCHYARD011602: Model [org.switchyard.config.model.switchyard.v1.V1SwitchYardModel] is invalid: cvc-complex-type.4: Attribute 'targetNamespace' must appear on element 'composite'. -> [Help 1]
The issue here is that the project contains no switchyard.xml, which is required for all SY applications. The targetNamespace value is determined based purely on the composite definition in the src/ version of switchyard.xml. There are two fixes for this issue: 1) Disable validation for switchyard-plugin in the pom.xml. This will allow the build to complete, but the resulting application may not function correctly as a SY deployment. If the purpose of this QS is to simply load the app in S-RAMP, then it probably doesn't matter. 2) Add a switchyard.xml to src/main/resources/META-INF which contains a <switchyard> element and a <composite> element which have name and targetNamespace attributes defined.
After diving into this a little bit it turns out that there *is* in fact a switchyard.xml file in the source for that demo: https://github.com/jboss-integration/s-ramp/blob/0.3.0.Final-prod-ip6.0/s-ramp-demos/s-ramp-demos-switchyard/src/main/resources/META-INF/switchyard.xml However, when creating the s-ramp-distro-assembly-demos kit (used by productization to include the demos in the product) we were previously excluding everything in META-INF (not sure why, probably a copy/paste error). However, Kurt recently fixed that problem here: https://github.com/jboss-integration/s-ramp/commit/a62a67db2bf078ef9d073759513a0d3406fb4321#diff-9e7f5a680aee3ae5fb5bf6fed97ffe79 This fix was included in the ER8-2 tag. Perhaps the wrong tag was used to build ER8, or else a new build hasn't been produced yet. Marking this as modified so it is retested in the next ER8 build.
Kurt's fix was for 1041334, which is why this issue was previously closed as a duplicate of that BZ. 1041334 has been verified as fixed in ER8. Can you check the current ER8 build and see if this problem exists? If it doesn't then please close this bug as a duplicate of 1041334.
Closing as duplicate of 1041334 *** This bug has been marked as a duplicate of bug 1041334 ***