[JENA-1917] Prepare FileManager for removal from public API.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: Jena 3.15.0
• Fix Version/s: Jena 3.16.0
• Component/s: Core
• Assignee: Andy Seaborne
• Reporter: Andy Seaborne
• Created: 15/Jun/20 09:57
• Updated: 13/Jul/20 15:51
• Resolved: 21/Jun/20 08:58

Description

This is preparation work for a clearup of FileManager.

Applications should not be using (jena-core) FileManager directly - there is equivalent functionality for remapping in RIOT and the read caching is  separated out in RIOT.

Long term, FileManager can be removed from general use. It is used by the OntDocumentManager so making solely for that purpose, maybe moving it to the "ont" sub-system.

The first step is to mark access via FileManager.get() as deprecated to signal future change. Also, mark the operations "readModel", "loadModel" that are better done with RDFDataMgr anyway.

Within Jena, clean up and switch to an access function that has the name "Internal" in it : FileManager.getInternal()

There are assemblers for FileManager and (jena-core) LocationMapper. We don't have an easy way to signal deprecation. They are used for OntDocumentManager. 

In the documentation:

• documentation/notes/file-manager.html

• assembler: only mention in the documentation for OntDocumentManager assembly.

and a few mentions in usage examples elsewhere.