Hey Evgeny,

Hmm ... I wonder if there's something with the plugin that's causing this issue.  I was able to create a new app from scratch with 0.3.0.Final and followed your steps using Forge.  I then opened the project in Eclipse and I see no validation errors with the generated switchyard.xml in the target directory.  I'm sure Rob (our resident tools expert) will chime in with some advice to troubleshoot further.

In the meantime, I wouldn't let this hold you back.  If the error is local to the Eclipse plugin (which I think it is), you should be able to move forward with creating and testing your app while ignoring the schema validation error.  Interesting side note - we schema validate the switchyard.xml inside our test kit, so you know if a test passes that the descriptor is legit.

BTW, if you're curious what the forge commands were to go through steps 1-4:

forge
new-project --named validateApp --topLevelPackage org.example.validateApp
project install-facet switchyard.bean
bean-service create --serviceName Example

I have attached the application I mentioned above in case you want to check it out in your Eclipse install.  Let us know if you also see validation errors with this one.

cheers,

keith

I can confirm that when I enable the Utility facet on the project, I also see the validation error.  I'll let Rob comment on whether our Eclipse support is compatible with this facet.  Do you need the Utility Module facet for something in particular?

Hey Evgeny,

Sorry for not spotting this sooner.  Could you confirm that you've disabled "Honour all XML schema locations" in the XML validation preferences (XML->XML Files->Validation)?  That should clear up the error.

Best,

Rob