Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Rejected
-
Affects Version/s: 0.2
-
Fix Version/s: None
-
Component/s: configuration, tooling
-
Labels:None
-
Estimated Difficulty:Low
Description
Similar to how the ConfigureMojo of the Maven SwitchYard plugin validates the outputted model configuration xml by default, but has an option to disable it, the SwitchYardFacet should also validate it's outputted xml, most likely triggered by writeSwitchYardConfig(). It is important that this can be disabled, though, in case the user plans on post-processing the xml to make it valid. Here is how the ConfigureMojo does it: http://goo.gl/Kgebe
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Bumping from 0.3 unless we determine this is a critical need for the current release.
Show
Keith Babo
added a comment - Bumping from 0.3 unless we determine this is a critical need for the current release.
Keith Babo
added a comment - Bumping from 0.3 unless we determine this is a critical need for the current release. After more consideration, I agree with Keith that this is not necessary.
Show
David Ward
added a comment - After more consideration, I agree with Keith that this is not necessary.
David Ward
added a comment - After more consideration, I agree with Keith that this is not necessary. 
Do we need to do this again in the forge tooling? Config is already validated every time you build an application or run a test. I think it's definitely a good idea to have unit tests for the forge tooling which test for schema validity, but not sure this is necessary when users actually use the tooling.