[
https://issues.apache.org/jira/browse/JENA-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370332#comment-14370332
]
Andy Seaborne commented on JENA-889:
------------------------------------
Thank you for the examples. The issue is not the {{LocationMapper}} but with
the {{LocatorClassLoader}} as you correctly diagnose.
Jena 2.6.4 was quite some time ago (before Apache for Jena).
The actual change happened 2014-01-15 (first release after that was Jena
2.11.1) in JENA-621. From what I can tell/remember, the issue was around the
fact that file:ont-policy.rdf was being picked up from the classpath and that
being confusing because the URL scheme "file:" implied a real filesystem file.
LocatorClassLoader is last on the default lookup chain which is used by the
ontology manager. There is always a "ont-policy.rdf" built-into Jena so
"file:ont-policy.rdf" always is found.
The correct form is "foo.ttl" - the fact that the old LocatorClassLoader
handled this was, arguably, a bug, although one that had been around for a long
time.
Changing back destabilizes the ontology manager. I'm minded to not revert to
the old behaviour. Other options are more widespread changes where current
users are not aware that mapping/locating are going on.
> FileManager/LocationMapper does not work with file: prefix for
> LocatorClassLoader
> ---------------------------------------------------------------------------------
>
> Key: JENA-889
> URL: https://issues.apache.org/jira/browse/JENA-889
> Project: Apache Jena
> Issue Type: Bug
> Components: Jena
> Affects Versions: Jena 2.12.1, Jena 2.13.0
> Reporter: Jan Vlug
> Attachments: locatortest.tar.bz
>
>
> I tried to use a LocationMapper configuration file as described at:
> https://jena.apache.org/documentation/notes/file-manager.html. This worked
> fine in an old Jena version. But now I upgraded to 2.12.1 it seems that I
> have to omit the file: prefix in the mapped URL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
