-
1. Re: bean scanner trigger
dward Aug 13, 2013 11:05 AM (in response to jaehui)1 of 1 people found this helpfulDo you have the BeanSwitchYardScanner set up in your switchyard:configure maven plugin (in your pom.xml)?
If not, you should add it. If so, try a clean before your build. i.e.: "mvn clean install"
Also, and this might be what you're experiencing…
The output of the eclipse tooling will overwrite src/main/resources/META-INF/switchyard.xml.
However, the output of mvn running the scanner(s) will be target/classes/META-INF/switchyard.xml. So, look there too.
-
2. Re: bean scanner trigger
rcernich Aug 13, 2013 11:15 AM (in response to jaehui)If you are using the SwitchYard tooling, the Eclipse auto-build will compile the modified file, which will trigger execution of the SwitchYard configure goal defined in your pom. If you edit the file outside Eclipse, you will have to manually build your project (as David suggested) or refresh the modified file in your Eclipse workspace.
Hope that helps,
Rob
-
3. Re: bean scanner trigger
jaehui Aug 13, 2013 11:58 AM (in response to rcernich)1 of 1 people found this helpfulSo it is the build that triggers it. Thanks.