[ 
https://issues.apache.org/jira/browse/JENA-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Vesse updated JENA-1264:
----------------------------
    Description: 
Having recently upgraded to Jena 3 internally one of our developers discovered 
a regression with regards to the ability to use 
{{RDFLanguages.langForContentType()}} to get a language for content types 
pertaining to SPARQL Results.

Debugging this in the Jena code shows that {{ResultSetLang.init()}} is never 
called by Jena initialisation so in users must call it manually. So we have a 
workaround for our code but ideally this should happen automatically as part of 
system initialisation.

  was:
Having recently upgraded to Jena 3 internally one of our developers discovered 
a regression with regards to the ability to use 
{{RDFLanguages.langForContentType()}} to get a language for content types 
pertaining to SPARQL Results.

Debugging this in the Jena code shows that `ResultSetLang.init()` is never 
called by Jena initialisation so in users must call it manually. So we have a 
workaround for our code but ideally this should happen automatically as part of 
system initialisation.


> ARQ initialisation fails to call ResultSetLang.init()
> -----------------------------------------------------
>
>                 Key: JENA-1264
>                 URL: https://issues.apache.org/jira/browse/JENA-1264
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ
>    Affects Versions: Jena 3.1.1
>            Reporter: Rob Vesse
>            Assignee: Rob Vesse
>             Fix For: Jena 3.2.0
>
>
> Having recently upgraded to Jena 3 internally one of our developers 
> discovered a regression with regards to the ability to use 
> {{RDFLanguages.langForContentType()}} to get a language for content types 
> pertaining to SPARQL Results.
> Debugging this in the Jena code shows that {{ResultSetLang.init()}} is never 
> called by Jena initialisation so in users must call it manually. So we have a 
> workaround for our code but ideally this should happen automatically as part 
> of system initialisation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to