You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Grzegorz Grzybek (JIRA)" <ji...@apache.org> on 2017/09/26 07:37:00 UTC

[jira] [Commented] (ARIES-1723) Blueprint NamespaceHandler can't resolve XSD in offline mode

    [ https://issues.apache.org/jira/browse/ARIES-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180393#comment-16180393 ] 

Grzegorz Grzybek commented on ARIES-1723:
-----------------------------------------

I have these changes made to a class fixed with ARIES-1540:
{noformat}
* 195a95b32 - [ARIES-1682] Fallback to URL API if URI.resolve(systemId) is still relative (case of jar:file:) (7 months ago) <Grzegorz Grzybek>
* cd294ead5 - [ARIES-1503] Wrap bad behaving NamespaceHandlers to fix their behavior (12 months ago) <Guillaume Nodet>
* ff122ebcb - [ARIES-1574] Remove the reference to AutoCloseable in blueprint-core in order to maintain Java 1.6 compatibility. (1 year, 3 months ago) <John Ross>
* 91b7e4fe5 - [ARIES-1540] Blueprint NamespaceHandler can't resolve XSD in offline mode (1 year, 5 months ago) <Guillaume Nodet>
{noformat}

Which of the changes revert the behavior? We use blueprint-core 1.8.0 without offline problems... Do you have sample blueprint.xml which fails offline?

> Blueprint NamespaceHandler can't resolve XSD in offline mode
> ------------------------------------------------------------
>
>                 Key: ARIES-1723
>                 URL: https://issues.apache.org/jira/browse/ARIES-1723
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.8.0
>            Reporter: Pointbreak
>            Priority: Blocker
>
> When the NamespaceHandler is offline, it fails to resolve the XSD. This is the exact same bug that was resolved in ARIES-1540 (blueprint-core-1.6.2).
> The changes made in that fix seem to have been undone in later versions. Issue ARIES-1540 describes the issue, and contains the bugfix. If I look at the code for 1.8.0 the change of that fix can be applied with no changes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)