[
https://issues.apache.org/jira/browse/TUSCANY-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuhwei Lwo updated TUSCANY-1085:
--------------------------------
Attachment: patch-1085.1
I have attached a new copy of simple2.xsd and patch-1085.1 as my first try of
fixing this problem.
I have left "FHL" in the patch to indicate what I have changed. Basically, I
changed SDOXSDEcoreBuilder.java to look up types with their namespaces against
extendedMetaData instead from XSD information. Also, createFeature() was
changed to return the property with correct containment value if the XSD type
cannot be resolved which becomes XSDSimpleTypeDefinition.
This fix has passed all the SDO impl test cases. Unfortunately, there is more
work to do because the serialization doesn't serialize the correct namespace
prefix and uri.
Please feel free to review my code and jump in to help. Thanks.
> schemaLocation attribute in the <xsd:import> should be only a hint
> ------------------------------------------------------------------
>
> Key: TUSCANY-1085
> URL: https://issues.apache.org/jira/browse/TUSCANY-1085
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-SDO-Mx
> Reporter: Fuhwei Lwo
> Fix For: Java-SDO-Mx
>
> Attachments: org.apache.tuscany.sdo.test.SimpleDynamicTestCase.txt,
> patch-1085.1, simple2.xsd, simple2.xsd, SimpleDynamicTestCase.java
>
>
> Currently XSDHelper.define(InputStream inputStream, String schemaLocation)
> uses the second parameter to locate the importing XSD specified by the
> schemaLocation attribute. If the schemaLocation is incorrect, its whole
> namespace cannot be resolved.
> The SDO runtime should be able to look up the registered namespace and type
> even the xsd:import failed. Also, the users should be able to register their
> SDO types with their XSD referencing the sdoModel.xsd but without providing
> sdoModel.xsd in their applications because sdoModel.xsd is the SDO core model.
> I will attach a test case later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
