You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by "Jakob Frank (JIRA)" <ji...@apache.org> on 2014/02/07 10:08:19 UTC
[jira] [Updated] (MARMOTTA-437) RDFFormat.forFileName / forMIMEType
will be deprecated in Sesame 2.8
[ https://issues.apache.org/jira/browse/MARMOTTA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Frank updated MARMOTTA-437:
---------------------------------
Assignee: Jakob Frank (was: Sebastian Schaffert)
> RDFFormat.forFileName / forMIMEType will be deprecated in Sesame 2.8
> --------------------------------------------------------------------
>
> Key: MARMOTTA-437
> URL: https://issues.apache.org/jira/browse/MARMOTTA-437
> Project: Marmotta
> Issue Type: Task
> Components: KiWi Triple Store, Platform
> Affects Versions: trunk
> Reporter: Jakob Frank
> Assignee: Jakob Frank
> Priority: Minor
> Fix For: 3.3
>
>
> In Sesame 2.8, {{RDFFormat.forFileName}} and {{RDFFormat.forMIMEType}} will be deprecated in favour of {{Rio.getParserFormatForFileName}} and {{Rio.getParserFormatForMIMEType}} ([SES-2015|https://openrdf.atlassian.net/browse/SES-2015]).
> We should update to the Rio based access...
> {quote}
> Users should be using Rio.getParserFormatForFileName and Rio.getParserFormatForMIMEType to pick up all of the RDFFormat's available on their classpath. RDFFormat.forFileName does not check the classpath for new RDFFormat definitions, resulting in users wondering why their third-party RDFFormat definitions do not appear.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)