[jira] Reopened: (COCOON3-2) Add an XSchema Validator as PipeLineComponent
[ https://issues.apache.org/jira/browse/COCOON3-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reopened COCOON3-2: -- Thanks for your contribution. I will have a look at it asap. Add an XSchema Validator as PipeLineComponent - Key: COCOON3-2 URL: https://issues.apache.org/jira/browse/COCOON3-2 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: SchemaProcessorInSiteMap.patch, XSchemaProcessor.patch XSchema Validation can be performed as an Identity Transformer where the input will be filter by the XSchema validation. An error occurs - and the pipeline will be break - when the input is not valid against the declared XML Schema. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (COCOON3-2) Add an XSchema Validator as PipeLineComponent
[ https://issues.apache.org/jira/browse/COCOON3-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reopened COCOON3-2: -- Simone, can you explain what the SchemaErrorHandler is supposed to do? Steven and I don't understand why it keeps references to raised exceptions. Also the getThrowable() method isn't used (which is actually not possible because the SchemaErrorHandler is created inline without keeping a reference to it in the transformer. Add an XSchema Validator as PipeLineComponent - Key: COCOON3-2 URL: https://issues.apache.org/jira/browse/COCOON3-2 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: XSchemaProcessor.patch XSchema Validation can be performed as an Identity Transformer where the input will be filter by the XSchema validation. An error occurs - and the pipeline will be break - when the input is not valid against the declared XML Schema. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
