[jira] Closed: (TUSCANY-2293) Assembly-xsd module defines xsds in the default package

["Rajini Sivaram (JIRA)" <tu...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram closed TUSCANY-2293.
-----------------------------------

    Resolution: Fixed
      Assignee: Rajini Sivaram

Temporary fix to use TCCL to load the schema applied under revision 654236.

But I agree with Hasan (https://issues.apache.org/jira/browse/TUSCANY-2295) that schema loading should use extension points.

> Assembly-xsd module defines xsds in the default package
> -------------------------------------------------------
>
>                 Key: TUSCANY-2293
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2293
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model
>    Affects Versions: Java-SCA-1.2
>            Reporter: Rajini Sivaram
>            Assignee: Rajini Sivaram
>            Priority: Minor
>             Fix For: Java-SCA-Next
>
>
> All xsds in assembly-xsd are defined in the default package.
> tuscany-sca.xsd  is currently read by ReallySmallRuntimeBuilder using the following code:
>     ReallySmallRuntimeBuilder.class.getClassLoader().getResource("tuscany-sca.xsd");
> For this code to work under OSGi, ReallySmallRuntimeBuilder has to be in the same bundle as tuscany-sca.xsd.
> To enable Tuscany modules to be built as separate OSGi bundles, either this classloading needs to be modified (to use Thread context classloader perhaps), or the xsd needs to move into a package (which can then be imported by host-embedded).
> The use of default package should be avoided wherever possible...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.