[
https://issues.apache.org/jira/browse/TUSCANY-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862155#action_12862155
]
Simon Laws commented on TUSCANY-3291:
-------------------------------------
I'm not convinced though that this works in 2.x for resolving stand alone
schema. In XSDModelResolver.resolveModel() it looks in it's local chache but I
don't see logic that is going to get it to look in other contributions via
"import". There is logic in URIResolverImpl but, as this is added into the
schema collection, this is employed when an existing schema has an
include/import that has to be resolved. I'm looking at the scenario where a
property type references a schema that's not in the current contribution. The
map is checked, there is nothing there so the schema is marked as unresolved.
> WSDL and XSD model resolvers do not use namespace imports
> ---------------------------------------------------------
>
> Key: TUSCANY-3291
> URL: https://issues.apache.org/jira/browse/TUSCANY-3291
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
> Affects Versions: Java-SCA-1.5
> Reporter: Brent Daniel
>
> This has been fixed in the 2.x branch but still exists in 1.5.1 and 1.x. [1]
> Namespace imports are not used in XSDModelResolver or WSDLModelResolver.
> The code to resolve namespace imports exists in both classes, but is not
> reachable because a ContributionRuntimeException will be thrown before
> reaching it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
