Deprecate RDFFormat.forFileName and RDFFormat.forMIMEType
Peter Ansell
Branch: SES-2015
SES-2015
Branch: 2.8.x
2.8.x
Merged
#244 · Created  · Last updated
Merged pull request
Merged in SES-2015 (pull request #244)
fa46c0e·Author: Peter Ansell·Closed by: Peter Ansell·2014-02-09
Description
This Pull Request deprecates RDFFormat.forFileName and RDFFormat.forMIMEType for Sesame-2.8.0.
It also makes them work slightly better by calling them from the registries, as an interim measure while users recognise the deprecation and move to using the dynamic methods in Rio.
The changes to RDFParserRegistry and RDFWriterRegistry do not fully fix the issue that users have consistently found with third-party instances of RDFFormat, as the registries are not likely to be initialised before the user calls the RDFFormat methods for the first time. This results in them wondering why it works the second time, but not the first time.
Adding the Marmotta developers as reviewers as that is where the issue came up last time, and I noticed a commit that used RDFFormat.forFileName again today:
This Pull Request deprecates RDFFormat.forFileName and RDFFormat.forMIMEType for Sesame-2.8.0.
It also makes them work slightly better by calling them from the registries, as an interim measure while users recognise the deprecation and move to using the dynamic methods in Rio.
The changes to RDFParserRegistry and RDFWriterRegistry do not fully fix the issue that users have consistently found with third-party instances of RDFFormat, as the registries are not likely to be initialised before the user calls the RDFFormat methods for the first time. This results in them wondering why it works the second time, but not the first time.
Adding the Marmotta developers as reviewers as that is where the issue came up last time, and I noticed a commit that used RDFFormat.forFileName again today:
https://github.com/apache/marmotta/commit/f53b62551b7ad0bd99f245e8b50645d0bf8a76d9#comments