[
https://issues.apache.org/jira/browse/TUSCANY-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TUSCANY-2295.
--------------------------------------
Resolution: Fixed
Fixed by using DefaultValidationSchemaExtensionPoint that will allow modules to
contribute validation schemas by specifying a
META-INF\services\org.apache.tuscany.sca.contribution.processor.ValidationSchema
file with a list of schemas as its contents.
> Tuscany should allow plugins to load their schemas instead of tuscany schema
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-2295
> URL: https://issues.apache.org/jira/browse/TUSCANY-2295
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Embedded Runtime
> Environment: All
> Reporter: Hasan Muhammad
> Assignee: Luciano Resende
> Priority: Critical
> Fix For: Java-SCA-Next
>
>
> Looking at the following code, the schema path is hardcoded, which means that
> plugins need to change this code everytime to load their schemas. Tuscany
> should allow plugins to point to their schemas without modifying this code
> // Allow privileged access to load resource. Requires
> RuntimePermssion in security policy.
> URL schemaURL = AccessController.doPrivileged(new
> PrivilegedAction<URL>() {
> public URL run() {
> return
> ReallySmallRuntimeBuilder.class.getClassLoader().getResource("tuscany-sca.xsd");
> }
> });
> Loading schemas should be an extension point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
