[
https://issues.apache.org/jira/browse/MARMOTTA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894351#comment-13894351
]
ASF subversion and git services commented on MARMOTTA-437:
----------------------------------------------------------
Commit 4b2a9ad753d5583131429ad7f1b63a80da16c068 in branch refs/heads/develop
from [~jakob]
[ https://git-wip-us.apache.org/repos/asf?p=marmotta.git;h=4b2a9ad ]
MARMOTTA-437: replaced RDFFormat.forFileName / forMIMEType with their
Rio-successors.
> 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)
