SwitchYardRunner fails because of unfiltered switchyard.xml

[edevera]

On my project we are using Maven filters in order to have the right values of the configuration items processed at build time. This works perfectly for all projects but those that have a SwitchYardRunner based tests. It seems that the tests prefer going to the src/main/resources folder rather than to the target/classes one. Is this a known behavior? Is this desired?

Thanks!

[kcbabo]

Is this for switchyard.xml or for another resource? 

[edevera]

It is switchyard.xml unfiltered.

[kcbabo]

The switchyard-plugin validates and serializes the config model to target/classes, so it could be that the plugin is picking up from src/main/resources at a time when filters have already created the filtered version in target/classes.  The plugin that serializes into target/classes, replacing the filtered resource.  Our test runner can be used to use alternate switchyard.xml definitions(you specify the path/name in the test) via the config element.  You can try using that to point to something like switchyard-filtered.xml which the SY plugin won't touch.  Another option would be to remove the switchyard-plugin and see what happens. :-)

[edevera]

Will the switchyard plugin read from the filtered switchyard.xml file at some point? Otherwise I think that using the switchyard plugin might make it impossible to have Maven filtering for switchyard configuration files. Right?

[dward]

You should be able to configure the plugin with different scan directories (and thus find a filtered switchyard.xml), per the mojo here: http://goo.gl/nbz2b

[tadayosi]

Hi Eduardo,

You might find the below forum discussion interesting:

"Maven resource filtering doesn't work in a SwitchYard project"

https://community.jboss.org/thread/228562