<?xml version="1.0" encoding="UTF-8" ?>




<!--  RSS generated by JIRA 108 at Thu Jun 20 04:11:06 CEST 2013 -->
<rss version="0.92">





<channel>
    <title>openRDF.org Issue Tracker</title>
    <link>http://www.openrdf.org/issues</link>
    <description>This file is an XML representation of some issues</description>
    <language>en</language>

    
<item>

    







<title>[SES-484] Add stringValue() to org.openrdf.model.Value as a substitute for the old toString() implementation</title>
<link>http://www.openrdf.org/issues/browse/SES-484</link>

    
        <description>The behaviour of Literal.toString() and BNode.toString() was changed in beta6 to make debugging easier (see &lt;a href=&quot;http://www.openrdf.org/issues/browse/SES-454&quot; title=&quot;BNode/Literal.toString() should print more complete description&quot;&gt;&lt;strike&gt;SES-454&lt;/strike&gt;&lt;/a&gt;). Although the behaviour of these methods was never specified in the RDF Model API, a lot of developers tended to use as a convenience method to retrieve a literal&apos;s label or a bnode&apos;s ID as it didn&apos;t require any casting. We should add a stringValue() method to the Value interface as a substitute for the old toString() implementation.&lt;br/&gt;
&lt;br/&gt;
This suggestion originally comes from the forum: &lt;a href=&quot;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1498#5596&quot;&gt;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1498#5596&lt;/a&gt;</description>
    
    
        <environment></environment>
    
        <key id="10808">SES-484</key>
        <summary>Add stringValue() to org.openrdf.model.Value as a substitute for the old toString() implementation</summary>
        <type id="2">New Feature</type>
    
        <priority id="5">Trivial</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Thu, 15 Nov 2007 15:59:17 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:16:33 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>RDF Model</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>1</votes>
    
    

    
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-452] Add support for @base directive to Turtle parser</title>
<link>http://www.openrdf.org/issues/browse/SES-452</link>

    
        <description>Dave Beckett added an @base directive to the Turtle specification on 2007/09/12. Support for this directive should be added to the Turtle parser.</description>
    
    
        <environment></environment>
    
        <key id="10772">SES-452</key>
        <summary>Add support for @base directive to Turtle parser</summary>
        <type id="2">New Feature</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Mon, 1 Oct 2007 10:52:26 +0200 (CEST)</created>
    <updated>Thu, 20 Mar 2008 20:15:26 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Rio</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-483] DirectTypeHierarchyInferencer is triggered too often</title>
<link>http://www.openrdf.org/issues/browse/SES-483</link>

    
        <description>The DirectTypeHierarchyInferencer currently recomputes the direct-* statements upon each commit. As a simple optimization, this process can be skipped unless an rdf:type, rdfs:subClassOf or rdfs:subPropertyOf statements was updated.</description>
    
    
        <environment></environment>
    
        <key id="10807">SES-483</key>
        <summary>DirectTypeHierarchyInferencer is triggered too often</summary>
        <type id="4">Improvement</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Thu, 15 Nov 2007 12:59:46 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:15:29 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Direct type hierarchy inferencer</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Thu, 15 Nov 2007 13:08:52 +0100 (CET)" level="">Fixed by checking which statements are reported as added/removed</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-485] Inline &quot;variable assigments&quot; in statement patterns</title>
<link>http://www.openrdf.org/issues/browse/SES-485</link>

    
        <description>The generic query optimizer should inline &amp;quot;variable assignments&amp;quot; in statement patterns to improve query evaluation performance. For example with the following SeRQL query:&lt;br/&gt;
&lt;br/&gt;
select *&lt;br/&gt;
from {X} P {Y}&lt;br/&gt;
where X = &amp;lt;&lt;a href=&quot;http://example.org&quot;&gt;http://example.org&lt;/a&gt;&amp;gt;&lt;br/&gt;
&lt;br/&gt;
To evaluate the (X, P, Y) statement pattern, it helps a lot to know that X should be equal &amp;lt;&lt;a href=&quot;http://example.org&quot;&gt;http://example.org&lt;/a&gt;&amp;gt; as it greatly reduces the search space for the pattern.This is a very common query pattern, therefor this optization should be implemented before 2.0-final, if possible.&lt;br/&gt;
&lt;br/&gt;
For comparison, Sesame 1.x does do this optimization and performance a lot better on this type of query. See the forum for some results: &lt;a href=&quot;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1506&quot;&gt;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1506&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
Care should be taken not to inline (literal) comparison. The query optimizer can, however, inline SameTerm operators. Comparison operators where one of the arguments is a URI or blank node can be converted to a SameTerm as a pre-processing step.</description>
    
    
        <environment></environment>
    
        <key id="10809">SES-485</key>
        <summary>Inline &quot;variable assigments&quot; in statement patterns</summary>
        <type id="4">Improvement</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Tue, 20 Nov 2007 08:58:33 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:15:32 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Query Optimizer</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-489] Add support for SPARQL-dataset loading</title>
<link>http://www.openrdf.org/issues/browse/SES-489</link>

    
        <description>Sesame currently supports querying of SPARQL-datasets, but it does not yet load the specified resources yet. This functionality is requried to implement SPARQL endpoints based on Sesame.</description>
    
    
        <environment></environment>
    
        <key id="10821">SES-489</key>
        <summary>Add support for SPARQL-dataset loading</summary>
        <type id="4">Improvement</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="james">James Leigh</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Fri, 23 Nov 2007 09:43:12 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:15:27 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Fri, 23 Nov 2007 09:56:21 +0100 (CET)" level="">The loading functionality has been implemented in the form of a DatasetRepository. This repository can be wrapped around a SailRepository and takes care of loading the resources specified in datasets into the wrapped repository.</comment>
            
            <comment author="herko_ter_horst" created="Fri, 23 Nov 2007 11:29:04 +0100 (CET)" level="">Please note that this functionality opens up the server to DoS attacks (by creating a query that potentially has to load many external resources) and possibly corrupt data from unknown sources. We should make sure this functionality can be disabled and/or controlled. In fact, it might be advisable to disable this functionality by default.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-493] Sesame server fails to handle (query-) post requests that specify a charset</title>
<link>http://www.openrdf.org/issues/browse/SES-493</link>

    
        <description>Issue reported here: &lt;a href=&quot;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1521&quot;&gt;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1521&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
Due to restrictions in the HTTP protocol, one can not use HTTP-GET requests to post queries containing non-ASCII characters. The best alternative is to use a POST-request and to encode the parameters in the request body. The MIME type for such requests is &amp;quot;application/x-www-form-urlencoded&amp;quot;. The Sesame HTTP server currently support this mechanism, but it fails when a specific character set is specified in the Content-Type header.</description>
    
    
        <environment></environment>
    
        <key id="10825">SES-493</key>
        <summary>Sesame server fails to handle (query-) post requests that specify a charset</summary>
        <type id="1">Bug</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Tue, 27 Nov 2007 14:22:01 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:16:28 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-beta3</version>
                
                    <version>2.0-beta4</version>
                
                    <version>2.0-beta5</version>
                
                    <version>2.0-beta6</version>
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>HTTP Server</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Thu, 29 Nov 2007 15:12:05 +0100 (CET)" level="">Content-Type headers are not properly parsed</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-491] OpenRDF Workbench fails to open when previously configured Sesame server is unavailable</title>
<link>http://www.openrdf.org/issues/browse/SES-491</link>

    
        <description>If OpenRDF Workbench was previously used on some Sesame server that is no longer available, but this server&apos;s URL is still stored in a browser&apos;s cookie, then Workbench fails to open with the stack trace shown below. As a workaround, one can remove the &amp;quot;server.select.url&amp;quot; as well as any &amp;quot;JSESSIONID&amp;quot; cookies from the browser&apos;s cache to enforce a new server selection.&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;HTTP Status 500 -&lt;br/&gt;
&lt;br/&gt;
------------------------------------------------------------------------&lt;br/&gt;
&lt;br/&gt;
*type* Exception report&lt;br/&gt;
&lt;br/&gt;
*message* __&lt;br/&gt;
&lt;br/&gt;
*description* _The server encountered an internal error () that&lt;br/&gt;
prevented it from fulfilling this request._&lt;br/&gt;
&lt;br/&gt;
*exception*&lt;br/&gt;
&lt;br/&gt;
org.apache.jasper.JasperException: javax.el.ELException: Error reading &apos;repositoryInfos&apos; on type org.openrdf.http.webclient.server.Server&lt;br/&gt;
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:541)&lt;br/&gt;
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:435)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:142)&lt;br/&gt;
	org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:247)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1123)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:860)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:774)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:460)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:415)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:690)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)&lt;br/&gt;
	org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)&lt;br/&gt;
	info.aduna.webapp.filters.ResourceRedirectFilter.doFilter(ResourceRedirectFilter.java:72)&lt;br/&gt;
&lt;br/&gt;
*root cause*&lt;br/&gt;
&lt;br/&gt;
javax.el.ELException: Error reading &apos;repositoryInfos&apos; on type org.openrdf.http.webclient.server.Server&lt;br/&gt;
	javax.el.BeanELResolver.getValue(BeanELResolver.java:66)&lt;br/&gt;
	javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)&lt;br/&gt;
	org.apache.el.parser.AstValue.getValue(AstValue.java:97)&lt;br/&gt;
	org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)&lt;br/&gt;
	org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923)&lt;br/&gt;
	org.apache.jsp.WEB_002dINF.views.server.overview_jsp._jspx_meth_c_005fforEach_005f4(overview_jsp.java:2627)&lt;br/&gt;
	org.apache.jsp.WEB_002dINF.views.server.overview_jsp._jspService(overview_jsp.java:339)&lt;br/&gt;
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:142)&lt;br/&gt;
	org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:247)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1123)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:860)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:774)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:460)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:415)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:690)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)&lt;br/&gt;
	org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)&lt;br/&gt;
	info.aduna.webapp.filters.ResourceRedirectFilter.doFilter(ResourceRedirectFilter.java:72)&lt;br/&gt;
&lt;br/&gt;
*root cause*&lt;br/&gt;
&lt;br/&gt;
org.openrdf.repository.RepositoryException: java.io.IOException: Failed to get query result from server: /openrdf-sesame/repositories&lt;br/&gt;
	org.openrdf.repository.manager.RemoteRepositoryManager.createRepositoryInfos(RemoteRepositoryManager.java:172)&lt;br/&gt;
	org.openrdf.repository.manager.RepositoryManager.getRepositoryInfoMap(RepositoryManager.java:307)&lt;br/&gt;
	org.openrdf.repository.manager.RepositoryManager.getAllRepositoryInfos(RepositoryManager.java:291)&lt;br/&gt;
	org.openrdf.http.webclient.server.Server.getRepositoryInfos(Server.java:52)&lt;br/&gt;
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&lt;br/&gt;
	sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)&lt;br/&gt;
	sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)&lt;br/&gt;
	java.lang.reflect.Method.invoke(Unknown Source)&lt;br/&gt;
	javax.el.BeanELResolver.getValue(BeanELResolver.java:62)&lt;br/&gt;
	javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)&lt;br/&gt;
	org.apache.el.parser.AstValue.getValue(AstValue.java:97)&lt;br/&gt;
	org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)&lt;br/&gt;
	org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923)&lt;br/&gt;
	org.apache.jsp.WEB_002dINF.views.server.overview_jsp._jspx_meth_c_005fforEach_005f4(overview_jsp.java:2627)&lt;br/&gt;
	org.apache.jsp.WEB_002dINF.views.server.overview_jsp._jspService(overview_jsp.java:339)&lt;br/&gt;
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:142)&lt;br/&gt;
	org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:247)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1123)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:860)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:774)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:460)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:415)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:690)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)&lt;br/&gt;
	org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)&lt;br/&gt;
	info.aduna.webapp.filters.ResourceRedirectFilter.doFilter(ResourceRedirectFilter.java:72)&lt;br/&gt;
&lt;br/&gt;
*root cause*&lt;br/&gt;
&lt;br/&gt;
java.io.IOException: Failed to get query result from server: /openrdf-sesame/repositories&lt;br/&gt;
	org.openrdf.http.client.HTTPClient.getTupleQueryResult(HTTPClient.java:1029)&lt;br/&gt;
	org.openrdf.http.client.HTTPClient.getRepositoryList(HTTPClient.java:367)&lt;br/&gt;
	org.openrdf.http.client.HTTPClient.getRepositoryList(HTTPClient.java:350)&lt;br/&gt;
	org.openrdf.repository.manager.RemoteRepositoryManager.createRepositoryInfos(RemoteRepositoryManager.java:143)&lt;br/&gt;
	org.openrdf.repository.manager.RepositoryManager.getRepositoryInfoMap(RepositoryManager.java:307)&lt;br/&gt;
	org.openrdf.repository.manager.RepositoryManager.getAllRepositoryInfos(RepositoryManager.java:291)&lt;br/&gt;
	org.openrdf.http.webclient.server.Server.getRepositoryInfos(Server.java:52)&lt;br/&gt;
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&lt;br/&gt;
	sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)&lt;br/&gt;
	sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)&lt;br/&gt;
	java.lang.reflect.Method.invoke(Unknown Source)&lt;br/&gt;
	javax.el.BeanELResolver.getValue(BeanELResolver.java:62)&lt;br/&gt;
	javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)&lt;br/&gt;
	org.apache.el.parser.AstValue.getValue(AstValue.java:97)&lt;br/&gt;
	org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)&lt;br/&gt;
	org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:923)&lt;br/&gt;
	org.apache.jsp.WEB_002dINF.views.server.overview_jsp._jspx_meth_c_005fforEach_005f4(overview_jsp.java:2627)&lt;br/&gt;
	org.apache.jsp.WEB_002dINF.views.server.overview_jsp._jspService(overview_jsp.java:339)&lt;br/&gt;
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)&lt;br/&gt;
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:142)&lt;br/&gt;
	org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:247)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1123)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:860)&lt;br/&gt;
	org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:774)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:460)&lt;br/&gt;
	org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:415)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:690)&lt;br/&gt;
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)&lt;br/&gt;
	org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)&lt;br/&gt;
	org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)&lt;br/&gt;
	info.aduna.webapp.filters.ResourceRedirectFilter.doFilter(ResourceRedirectFilter.java:72)&lt;br/&gt;
&lt;br/&gt;
*note* _The full stack trace of the root cause is available in the&lt;br/&gt;
Apache Tomcat/6.0.13 logs._&lt;br/&gt;
&lt;br/&gt;
------------------------------------------------------------------------&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Apache Tomcat/6.0.13&lt;br/&gt;
&lt;br/&gt;
</description>
    
    
        <environment></environment>
    
        <key id="10823">SES-491</key>
        <summary>OpenRDF Workbench fails to open when previously configured Sesame server is unavailable</summary>
        <type id="1">Bug</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="herko_ter_horst">Herko ter Horst</assignee>
        
    

    
        
        <reporter username="chris">Christiaan Fluit</reporter>
        
    

        
        <created>Mon, 26 Nov 2007 14:08:23 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:15:34 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Web interface</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Mon, 26 Nov 2007 20:07:06 +0100 (CET)" level="">Reassigning this issue, need to learn more about Spring&apos;s exception handling mechanisms first.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-496] Update Turtle parser to 20 November 2007 specification</title>
<link>http://www.openrdf.org/issues/browse/SES-496</link>

    
        <description>Dave Beckett recently updated the Turtle spec. The changes brings the spec closer to how Sesame&apos;s Turlte parser treats Turtle data: canonicalization of integers and boolean is no longer required and white space is optional where possible.</description>
    
    
        <environment></environment>
    
        <key id="10828">SES-496</key>
        <summary>Update Turtle parser to 20 November 2007 specification</summary>
        <type id="3">Task</type>
    
        <priority id="4">Minor</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Fri, 30 Nov 2007 09:44:47 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:16:30 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Rio</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-476] OutOfMemoryError from MemoryStore.startSyncTimer</title>
<link>http://www.openrdf.org/issues/browse/SES-476</link>

    
        <description>I suspect, if the store is closed short after the sync thread was started but hasn&apos;t done something, then maybe these threads live on forever? Somehow th number of threads seems to grow too large.&lt;br/&gt;
&lt;br/&gt;
java.lang.OutOfMemoryError: unable to create new native thread&lt;br/&gt;
	at java.lang.Thread.start0(Native Method)&lt;br/&gt;
	at java.lang.Thread.start(Thread.java:574)&lt;br/&gt;
	at java.util.Timer.&amp;lt;init&amp;gt;(Timer.java:137)&lt;br/&gt;
	at java.util.Timer.&amp;lt;init&amp;gt;(Timer.java:106)&lt;br/&gt;
	at org.openrdf.sail.memory.MemoryStore.startSyncTimer(MemoryStore.java:723)&lt;br/&gt;
	at org.openrdf.sail.memory.MemoryStoreConnection.commitInternal(MemoryStoreConnection.java:285)&lt;br/&gt;
	at org.openrdf.sail.helpers.SailConnectionBase.commit(SailConnectionBase.java:255)&lt;br/&gt;
	at org.openrdf.repository.sail.SailRepositoryConnection.commit(SailRepositoryConnection.java:83)&lt;br/&gt;
	at org.openrdf.repository.base.RepositoryConnectionBase.autoCommit(RepositoryConnectionBase.java:211)&lt;br/&gt;
	at org.openrdf.repository.base.RepositoryConnectionBase.remove(RepositoryConnectionBase.java:481)&lt;br/&gt;
	at org.openrdf.rdf2go.RepositoryModel.removeStatement(RepositoryModel.java:312)&lt;br/&gt;
	at org.ontoware.rdf2go.model.impl.AbstractModelAddRemove.removeStatement(AbstractModelAddRemove.java:83)&lt;br/&gt;
	at org.ontoware.rdf2go.model.impl.AbstractModel.removeStatement(AbstractModel.java:399)&lt;br/&gt;
	at org.ontoware.rdf2go.model.impl.NotifyingModelLayer.removeStatement(NotifyingModelLayer.java:242)&lt;br/&gt;
	at org.ontoware.rdf2go.model.impl.NotifyingModelLayer.removeAll(NotifyingModelLayer.java:171)&lt;br/&gt;
	at org.ontoware.rdfreactor.runtime.Base.removeAll_unsynchronized(Base.java:125)&lt;br/&gt;
	at org.ontoware.rdfreactor.runtime.Base.set(Base.java:132)&lt;br/&gt;
	at org.semanticdesktop.swecr.model.rdf.generated.Relation.setInverse(Relation.java:88)&lt;br/&gt;
	at org.semanticdesktop.swecr.model.rdf.RelationOnCore.&amp;lt;init&amp;gt;(RelationOnCore.java:37)&lt;br/&gt;
	at org.semanticdesktop.swecr.model.rdf.SwcmOnRDF.createRelation(SwcmOnRDF.java:1122)&lt;br/&gt;
	at org.semanticdesktop.swecr.model.rdf.SwcmOnRDF.createRelation(SwcmOnRDF.java:1167)&lt;br/&gt;
	at org.semanticdesktop.swecr.model.util.RepositoryUtils.addTestData_manyStatements(RepositoryUtils.java:255)&lt;br/&gt;
</description>
    
    
        <environment>So far only reproducible in my application JUnit tests via the OpenRDF2Go driver. The longer the synchronisation delay, the higher the chances for this error. I can reproduce it deterministically. </environment>
    
        <key id="10800">SES-476</key>
        <summary>OutOfMemoryError from MemoryStore.startSyncTimer</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="xamde">Max V&#246;lkel</reporter>
        
    

        
        <created>Wed, 14 Nov 2007 13:27:13 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:15:00 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Memory Sail</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="xamde" created="Wed, 14 Nov 2007 14:02:01 +0100 (CET)" level="">This test reproduces the bug. Shorter sync times or fewer triple writes work fine.&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
import java.io.File;&lt;br/&gt;
&lt;br/&gt;
import org.junit.Test;&lt;br/&gt;
&lt;br/&gt;
import org.openrdf.model.Resource;&lt;br/&gt;
import org.openrdf.repository.Repository;&lt;br/&gt;
import org.openrdf.repository.RepositoryConnection;&lt;br/&gt;
import org.openrdf.repository.RepositoryException;&lt;br/&gt;
import org.openrdf.repository.sail.SailRepository;&lt;br/&gt;
import org.openrdf.sail.memory.MemoryStore;&lt;br/&gt;
&lt;br/&gt;
/**&lt;br/&gt;
&amp;nbsp;* &lt;br/&gt;
&amp;nbsp;* @author voelkel&lt;br/&gt;
&amp;nbsp;*/&lt;br/&gt;
public class OpenRdfTest {&lt;br/&gt;
&lt;br/&gt;
	@Test&lt;br/&gt;
	public void testMemoryStoreSync()&lt;br/&gt;
		throws RepositoryException&lt;br/&gt;
	{&lt;br/&gt;
		MemoryStore memoryStore = new MemoryStore();&lt;br/&gt;
		memoryStore.setSyncDelay(5 * 60 * 1000); // 5 minutes&lt;br/&gt;
		memoryStore.setPersist(true);&lt;br/&gt;
		File dataDir = new File(&amp;quot;./tmp/test&amp;quot;);&lt;br/&gt;
		memoryStore.setDataDir(dataDir);&lt;br/&gt;
		Repository repository = new SailRepository(memoryStore);&lt;br/&gt;
		repository.initialize();&lt;br/&gt;
		RepositoryConnection conn = repository.getConnection();&lt;br/&gt;
&lt;br/&gt;
		for (int j = 0; j &amp;lt; 10000; j++) {&lt;br/&gt;
			conn.add(repository.getValueFactory().createURI(&amp;quot;urn:s:&amp;quot; + System.currentTimeMillis() + &amp;quot;-&amp;quot; + j),&lt;br/&gt;
					repository.getValueFactory().createURI(&amp;quot;urn:p:&amp;quot; + System.currentTimeMillis() + &amp;quot;-&amp;quot; + j),&lt;br/&gt;
					repository.getValueFactory().createURI(&amp;quot;urn:o:&amp;quot; + System.currentTimeMillis() + &amp;quot;-&amp;quot; + j),&lt;br/&gt;
					new Resource[0]);&lt;br/&gt;
		}&lt;br/&gt;
&lt;br/&gt;
	}&lt;br/&gt;
&lt;br/&gt;
}&lt;br/&gt;
</comment>
            
            <comment author="arjohn" created="Thu, 15 Nov 2007 13:35:46 +0100 (CET)" level="">This may be related to the new &amp;quot;snapshots&amp;quot; functionality in the MemoryStore. Old snapshots should be cleaned up by a daemon thread  when there are no other threads that accesss the repository.</comment>
            
            <comment author="arjohn" created="Fri, 16 Nov 2007 20:43:17 +0100 (CET)" level="">Out-of-memory was caused by an exceptionally large amount of Timer threads, issue has been fixed by cancelling the TimerTask instead of the Timer itself. Fix is available as in revision 3566: &lt;a href=&quot;http://src.aduna-software.org/viewvc/org.openrdf/?rev=3566&amp;view=rev&quot;&gt;http://src.aduna-software.org/viewvc/org.openrdf/?rev=3566&amp;amp;view=rev&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
Max, can you confirm that this fixes the issue?</comment>
            
            <comment author="xamde" created="Mon, 19 Nov 2007 22:31:01 +0100 (CET)" level="">No, it doesn&apos;t fix the issue. You can add the code above to your test suite.</comment>
            
            <comment author="arjohn" created="Tue, 20 Nov 2007 07:31:48 +0100 (CET)" level="">That&apos;s strange, the above code run just fine now on my machine.</comment>
            
            <comment author="xamde" created="Tue, 20 Nov 2007 14:51:31 +0100 (CET)" level="">Maybe you have more RAM? Try running the same test with higher values for memoryStore.setSyncDelay(5 * 60 * 1000); // 5 minutes&lt;br/&gt;
or loop cycles.</comment>
            
            <comment author="arjohn" created="Fri, 23 Nov 2007 14:12:54 +0100 (CET)" level="">I did some tests this morning with the sync delay set to 15 minutes. Using the default memory size (128 MB?) I was able to run 70,000 iterations before running out of memory. With max memory set to 512 MB I was able to run 500,000 iterations, at which point the Java process consumed some 500 MB of memory. These look very reasonable results, any further out-of-memory problems are likely related to the amount of stored triples. These tests were run with all of the recent fixes to the MemoryStore, there may have been other fixes that affect memory usage.&lt;br/&gt;
&lt;br/&gt;
I consider this issue fixed as I didn&apos;t see any further &amp;quot;unable to create new native thread &amp;quot; errors while running the tests.</comment>
            
            <comment author="xamde" created="Mon, 26 Nov 2007 11:24:05 +0100 (CET)" level="">Confirm: fixed in RC2-SNAPSHOT</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-479] ORDER BY modifier does not always produce expected/correct results</title>
<link>http://www.openrdf.org/issues/browse/SES-479</link>

    
        <description>Running the query:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;select ?o { ?s ?p ?o } order by ?o&lt;br/&gt;
&lt;br/&gt;
on this set of triples:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;foo:bar1&amp;gt; &amp;lt;foo:prop3&amp;gt; &amp;quot;4&amp;quot;@en .&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;foo:bar2&amp;gt; &amp;lt;foo:prop2&amp;gt; &amp;quot;10&amp;quot;^^&amp;lt;&lt;a href=&quot;http://www.w3.org/2001/XMLSchema#int&quot;&gt;http://www.w3.org/2001/XMLSchema#int&lt;/a&gt;&amp;gt; .&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;foo:bar3&amp;gt; &amp;lt;foo:prop1&amp;gt; &amp;quot;9&amp;quot;^^&amp;lt;&lt;a href=&quot;http://www.w3.org/2001/XMLSchema#int&quot;&gt;http://www.w3.org/2001/XMLSchema#int&lt;/a&gt;&amp;gt; .&lt;br/&gt;
&lt;br/&gt;
produces the following result:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;quot;10&amp;quot;^^&amp;lt;&lt;a href=&quot;http://www.w3.org/2001/XMLSchema#int&quot;&gt;http://www.w3.org/2001/XMLSchema#int&lt;/a&gt;&amp;gt;&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;quot;4&amp;quot;@en&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;quot;9&amp;quot;^^&amp;lt;&lt;a href=&quot;http://www.w3.org/2001/XMLSchema#int&quot;&gt;http://www.w3.org/2001/XMLSchema#int&lt;/a&gt;&amp;gt;&lt;br/&gt;
&lt;br/&gt;
While the individual consecutive value pairs are ordered correctly (the order of literals with language tags and datatyped literals is not defined), the total result is not: &amp;quot;9&amp;quot;^^xsd:int should come before &amp;quot;10&amp;quot;^^xsd:int.&lt;br/&gt;
&lt;br/&gt;
FWIW: running this test through ARQ (tested with v2.1) produces the exact same (erroneous) result.</description>
    
    
        <environment></environment>
    
        <key id="10803">SES-479</key>
        <summary>ORDER BY modifier does not always produce expected/correct results</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="james">James Leigh</reporter>
        
    

        
        <created>Thu, 15 Nov 2007 10:01:58 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:56 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Query Engine</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Thu, 15 Nov 2007 11:51:32 +0100 (CET)" level="">The algorithm has been fixed by changing the order of literals, grouping all datatyped literals together. Within the group of datatypes literals, literals with compatible, ordered datatypes are again grouped together.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-480] NativeStore doesn&apos;t correctly report removed statements to SailConnectionListener&apos;s</title>
<link>http://www.openrdf.org/issues/browse/SES-480</link>

    
        <description></description>
    
    
        <environment></environment>
    
        <key id="10804">SES-480</key>
        <summary>NativeStore doesn&apos;t correctly report removed statements to SailConnectionListener&apos;s</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Thu, 15 Nov 2007 12:38:46 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:51 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Native Sail</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Thu, 15 Nov 2007 12:55:12 +0100 (CET)" level="">NativeStoreConnection.removeStatements(...) iterated over the wrong set of statements and reported these as removed.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-481] DirectTypeHierarchyInferencer doesn&apos;t initialize newly created repositories</title>
<link>http://www.openrdf.org/issues/browse/SES-481</link>

    
        <description>Newly created repositories that use the DirectTypeHierarchyInferencer do not initially contain the direct* properties. The DirectTypeHierarchyInferencer forgets to add these statements upon the first initialization of the repository.</description>
    
    
        <environment></environment>
    
        <key id="10805">SES-481</key>
        <summary>DirectTypeHierarchyInferencer doesn&apos;t initialize newly created repositories</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Thu, 15 Nov 2007 12:39:20 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:24 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Direct type hierarchy inferencer</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Thu, 15 Nov 2007 13:12:11 +0100 (CET)" level="">Fixed by running the inferencing in DirectTypeHierarchyInferencer.initialize().</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-487] MemoryStore.getContextIDs() sometimes returns IDs of cleared contexts</title>
<link>http://www.openrdf.org/issues/browse/SES-487</link>

    
        <description>Issue reported on the forum: &lt;a href=&quot;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1503&quot;&gt;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1503&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
&amp;quot;I&apos;ve just moved to 2.0-rc1 and I&apos;m seeing some strange synchronisation issues. Specifically:&lt;br/&gt;
&lt;br/&gt;
Create a repository containing statements with contexts (about 150 statements in this case)&lt;br/&gt;
Create a connection, clear(), commit(), close().&lt;br/&gt;
Open a new connection (in the same thread) and get the list of contexts.&lt;br/&gt;
&lt;br/&gt;
If this is done with no yeald or sleep I still see the old contexts that should have been cleared. If i sleep or single step in the debugger I see no contexts remaining.&amp;quot;&lt;br/&gt;
&lt;br/&gt;
...&lt;br/&gt;
&lt;br/&gt;
&amp;quot;Also calling clear() after the add but before the first commit doesn&apos;t seem to remove the contexts at all.&amp;quot;</description>
    
    
        <environment></environment>
    
        <key id="10811">SES-487</key>
        <summary>MemoryStore.getContextIDs() sometimes returns IDs of cleared contexts</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Wed, 21 Nov 2007 14:43:38 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:35 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Memory Sail</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Wed, 21 Nov 2007 20:27:24 +0100 (CET)" level="">MemoryStore.getContextIDs() ignored read-mode and snapshot parameters.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-486] NativeStore doesn&apos;t properly handle transaction with combined add &amp; remove operations</title>
<link>http://www.openrdf.org/issues/browse/SES-486</link>

    
        <description>The following JUnit test for the RepositoryConnectionTest  class fails on the NativeStore:&lt;br/&gt;
&lt;br/&gt;
	public void testAddRemove()&lt;br/&gt;
		throws Exception&lt;br/&gt;
	{&lt;br/&gt;
		URI FOAF_PERSON = vf.createURI(&amp;quot;&lt;a href=&quot;http://xmlns.com/foaf/0.1/Person&quot;&gt;http://xmlns.com/foaf/0.1/Person&lt;/a&gt;&amp;quot;);&lt;br/&gt;
		final Statement stmt = vf.createStatement(bob, name, nameBob);&lt;br/&gt;
&lt;br/&gt;
		testCon.add(bob, RDF.TYPE, FOAF_PERSON);&lt;br/&gt;
&lt;br/&gt;
		testCon.setAutoCommit(false);&lt;br/&gt;
		testCon.add(stmt);&lt;br/&gt;
		testCon.remove(stmt);&lt;br/&gt;
		testCon.commit();&lt;br/&gt;
&lt;br/&gt;
		testCon.exportStatements(null, null, null, false, new RDFHandlerBase() {&lt;br/&gt;
&lt;br/&gt;
			@Override&lt;br/&gt;
			public void handleStatement(Statement st)&lt;br/&gt;
				throws RDFHandlerException&lt;br/&gt;
			{&lt;br/&gt;
				assertTrue(!stmt.equals(st));&lt;br/&gt;
			}&lt;br/&gt;
		});&lt;br/&gt;
	}</description>
    
    
        <environment></environment>
    
        <key id="10810">SES-486</key>
        <summary>NativeStore doesn&apos;t properly handle transaction with combined add &amp; remove operations</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="james">James Leigh</reporter>
        
    

        
        <created>Wed, 21 Nov 2007 12:33:00 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:53 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Native Sail</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Wed, 21 Nov 2007 14:24:46 +0100 (CET)" level="">The problem occurred when TripleStore used the updatedTriplesCache upon commit. This cache contains all updated triple records and is used to speed up (relatively) small updates. The were two problems with this cache:&lt;br/&gt;
1) The cache was a sequential list of triple records that contained duplicates&lt;br/&gt;
2) The commit is a two-stage process where the deprecated triples are discarded first, followed by a transaction flag-resetting phase of the rest of the statements. The latter stage comes down to simply inserting/overwriting the existing records with the cached records that have their flags reset. However, the records of the deprecated triples were not ignored during the second phase, with the result that these were re-added to the store.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-488] MemoryStore doesn&apos;t process &quot;statements neutral&quot; transactions correctly</title>
<link>http://www.openrdf.org/issues/browse/SES-488</link>

    
        <description>The MemoryStore doesn&apos;t correctly process transactions that do not affect the set of stored statements. Examples of this are transactions where a statement is added and removed in the same transaction, and transactions where an inferred statement is substituted by an explicit one (or vice versa). In those cases, MemoryStore doesn&apos;t increase the snapshot number for the store and it also doesn&apos;t schedule a snapshot cleanup.</description>
    
    
        <environment></environment>
    
        <key id="10820">SES-488</key>
        <summary>MemoryStore doesn&apos;t process &quot;statements neutral&quot; transactions correctly</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Thu, 22 Nov 2007 11:15:33 +0100 (CET)</created>
    <updated>Mon, 30 Jun 2008 17:06:09 +0200 (CEST)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Memory Sail</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
    

    



    <issuelinks>
    
        <issuelinktype id="10020">
            <name>Related</name>
                
                
                
                
                
                    <inwardlinks description="is related to">
                    
                        <issuelink>
                            <issuekey id="10893">SES-545</issuekey>
                        </issuelink>
                    
                    </inwardlinks>
                
                
        </issuelinktype>
    
    </issuelinks>


    
    
    

</item>
    
<item>

    







<title>[SES-492] TriX parser discard leading and trailing whitespace for literals</title>
<link>http://www.openrdf.org/issues/browse/SES-492</link>

    
        <description>Issue reported at &lt;a href=&quot;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1517&quot;&gt;http://www.openrdf.org/forum/mvnforum/viewthread?thread=1517&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
The following code snippet exports a statement to TriX and reads it back in. The assertion at the end fails:&lt;br/&gt;
&lt;br/&gt;
		URI subj = valueFactory.createURI(&amp;quot;&lt;a href=&quot;http://subj&quot;&gt;http://subj&lt;/a&gt;&amp;quot;);&lt;br/&gt;
		Literal literal = valueFactory.createLiteral(&amp;quot;text\n\n&amp;quot;);&lt;br/&gt;
		connection.add(subj, RDFS.LABEL, literal);&lt;br/&gt;
&lt;br/&gt;
		StringWriter sw = new StringWriter();&lt;br/&gt;
		connection.export(new TriXWriter(sw));&lt;br/&gt;
&lt;br/&gt;
		connection.clear();&lt;br/&gt;
		connection.add(new StringReader(sw.toString()), null, RDFFormat.TRIX);&lt;br/&gt;
		assert literal.equals(connection.getStatements(subj, RDFS.LABEL, null, false).asList().get(0).getObject());</description>
    
    
        <environment></environment>
    
        <key id="10824">SES-492</key>
        <summary>TriX parser discard leading and trailing whitespace for literals</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Tue, 27 Nov 2007 11:52:38 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:15:01 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-alpha-1</version>
                
                    <version>2.0-alpha-2</version>
                
                    <version>2.0-alpha-3</version>
                
                    <version>2.0-alpha-4</version>
                
                    <version>2.0-beta1</version>
                
                    <version>2.0-beta2</version>
                
                    <version>2.0-beta3</version>
                
                    <version>2.0-beta4</version>
                
                    <version>2.0-beta5</version>
                
                    <version>2.0-beta6</version>
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Rio</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Tue, 27 Nov 2007 13:34:39 +0100 (CET)" level="">The TriXParser now preserves leading and trailing whitespace characters for XML text elements.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-490] MemoryStore&apos;s leaves a running file sync thread after being shut down</title>
<link>http://www.openrdf.org/issues/browse/SES-490</link>

    
        <description>The MemoryStore uses a separate thread for delayed file synchronization if such behaviour is specified using the syncDelay parameter. This thread, however, keeps running even after the store has been shut down. This running thread prevents a normal exit of the JVM.&lt;br/&gt;
&lt;br/&gt;
This problem was likely introduced while fixing &lt;a href=&quot;http://www.openrdf.org/issues/browse/SES-476&quot; title=&quot;OutOfMemoryError from MemoryStore.startSyncTimer&quot;&gt;&lt;strike&gt;SES-476&lt;/strike&gt;&lt;/a&gt;.</description>
    
    
        <environment></environment>
    
        <key id="10822">SES-490</key>
        <summary>MemoryStore&apos;s leaves a running file sync thread after being shut down</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Fri, 23 Nov 2007 12:54:15 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:31 +0100 (CET)</updated>

    
        
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Memory Sail</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Fri, 23 Nov 2007 14:01:17 +0100 (CET)" level="">File synchronization thread is now a deamon thread, which is killed when shutDown() is called.&lt;br/&gt;
&lt;br/&gt;
Fixed in svn revision 3596.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
<item>

    







<title>[SES-478] Inferred statements not visible to connection during transaction</title>
<link>http://www.openrdf.org/issues/browse/SES-478</link>

    
        <description>The current inferencing Sails (only) apply their inferencing when commit is called. As a result of this, the (updated) inferred statements are not available during a transactions. For example, consider this code fragment:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;con.setAutoCommit(false);&lt;br/&gt;
&amp;nbsp;&amp;nbsp;con.add(....);&lt;br/&gt;
&amp;nbsp;&amp;nbsp;con.remove(...);&lt;br/&gt;
&amp;nbsp;&amp;nbsp;con.getStatements(..., true);&lt;br/&gt;
&amp;nbsp;&amp;nbsp;con.setAutoCommit(true);&lt;br/&gt;
&lt;br/&gt;
The results returned by getStatements(...) are based on the data that was available before the transaction started, and are thus out of date, at least as far as this connection is concerned.</description>
    
    
        <environment></environment>
    
        <key id="10802">SES-478</key>
        <summary>Inferred statements not visible to connection during transaction</summary>
        <type id="1">Bug</type>
    
        <priority id="3">Major</priority>
    
        <status id="6">Closed</status>
        
        <resolution id="1">Fixed</resolution>
        
    
        
        <assignee username="arjohn">Arjohn Kampman</assignee>
        
    

    
        
        <reporter username="arjohn">Arjohn Kampman</reporter>
        
    

        
        <created>Wed, 14 Nov 2007 13:39:16 +0100 (CET)</created>
    <updated>Thu, 20 Mar 2008 20:14:26 +0100 (CET)</updated>

    
        
        
            
            
                
                    <version>2.0-rc1</version>
                
            
        
    

    
        
        
            
            
                
                    <fixVersion>2.0-rc2</fixVersion>
                
            
        
    

    
        
        
            
            
                
                    <component>Direct type hierarchy inferencer</component>
                
                    <component>RDF Schema inferencer (forward-chaining)</component>
                
            
        
    

    
    
        <due></due>
    
    
        <votes>0</votes>
    
    

    
    
        <comments>
            
            <comment author="arjohn" created="Thu, 15 Nov 2007 13:10:19 +0100 (CET)" level="">Fixed by intermediate flushing of inferencer results when amethod that read statements is called.</comment>
            
        </comments>
    
    

    




    
    
    

</item>
    
</channel>
</rss>  

