Mulgara Project: Issueshttps://code.mulgara.org/https://code.mulgara.org/favicon.ico?15861924492012-02-07T21:37:21ZMulgara Project
Redmine Mulgara - Bug #213 (New): Error on ORDER BY variables projected away by SELECT clausehttps://code.mulgara.org/issues/2132012-02-07T21:37:21ZAlex Hall -alexhall@revelytix.com
<p>A SPARQL query that mentions a variable in an ORDER BY expression that appears in the WHERE clause but is projected away by the SELECT clause incorrectly causes an exception to be thrown. According to SPARQL, ordering is applied prior to projection, so this should be valid. This appears to be a case where TQL and SPARQL semantics are mis-aligned.</p> Mulgara - Bug #206 (New): MulgaraUserConfig uses system classloader for conf/mulgara-x-config.xmlhttps://code.mulgara.org/issues/2062009-09-27T18:54:16ZKarsten Huneycutt -kph@skuld.us
<p>The <a class="wiki-page new" href="https://code.mulgara.org/projects/mulgara/wiki/MulgaraUserConfig">MulgaraUserConfig</a> class uses the system class loader to find conf/mulgara-x-config.xml. In some cases, the system class loader is not necessarily the class loader that was used to load the mulgara jar, so it is unable to find the config file that is in the mulgara jar.</p>
<p>The simple fix is to change </p>
<pre><code>URL sysUrl = [[ClassLoader]].getSystemResource(CONFIG_PATH);</code></pre>
<p>to</p>
<pre><code>URL sysUrl = this.getClass().getClassLoader().getResource(CONFIG_PATH);</code></pre>
<p>in src/jar/server/java/org/mulgara/server/MulgaraUserConfig.java, line 89.</p> Mulgara - Feature #198 (New): SPARQL XML results encodinghttps://code.mulgara.org/issues/1982009-09-01T20:02:05ZGregg -gar@foo.bar
<p>Currently the XML response to SPARQL queries does not specify an encoding in the XML header. The SPARQL Protocol definition doesn't seem to address this, and the examples omit it; but the SOAP example includes it. As a matter of "best practice" I think Mulgara should always explicitly indicate the encoding.</p> Mulgara - Bug #195 (New): Server IO Exceptionhttps://code.mulgara.org/issues/1952009-08-29T16:45:42ZGregg -gar@foo.bar
<p>I'm see the server dump a stack frame when I run a query using curl. I'm trying to query the system graph, on a freshly installed server with no loaded graphs. I don't know if I'm doing this right, but I don't think the server should barf. The curl file is:<br /><pre>
--url = "http://localhost:8080/sparql/"
--include
--header "Accept: application/sparql-results+xml"
--get
--data-urlencode "query=select ?x ?y ?z where {?x ?y ?z}"
--data-urlencode "default-graph-uri=http://localhost:8080/#"
</pre></p>
<p>mulgara.log says:<br /><pre>
2009-08-29 11:37:56,505 WARN [btpool0-17 - /sparql/?query=select%20%3Fx%20%3Fy%20%3Fz%20where%20%7B%3Fx%20%3Fy%20%3Fz%7D&default-graph-uri=http%3A%2F%2Flocalhost%3A8080%2F%23] http.HttpContent - Ignoring bad parameters in ' charset=iso-8859-1' from the content type for http://localhost:8080/#
2009-08-29 11:37:56,512 WARN [btpool0-17 - /sparql/?query=select%20%3Fx%20%3Fy%20%3Fz%20where%20%7B%3Fx%20%3Fy%20%3Fz%7D&default-graph-uri=http%3A%2F%2Flocalhost%3A8080%2F%23] http.HttpContent - Ignoring bad parameters in ' charset=iso-8859-1' from the content type for http://localhost:8080/#
2009-08-29 11:37:56,863 WARN [Thread-46] rdfxml.Parser - Recoverable error, line 1, column 122: {E213} Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.generalError(XMLHandler.java:197)
at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:113)
at com.hp.hpl.jena.rdf.arp.ARP.load(ARP.java:143)
at org.mulgara.content.rdfxml.Parser.run(Parser.java:297)
Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1305)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:106)
... 2 more
</pre></p> Mulgara - Bug #190 (New): tql swallows uri fragmentshttps://code.mulgara.org/issues/1902009-08-13T22:03:23ZPaula Gearon
<p>eg. In the following query result, the #all is missing<br /><pre>
itql> select $o from <local:///topazproject#grants> where $s $p $o
and $o <mulgara:is> <topaz:permissions#all>;
variables: {"o"}
cnt = 1
o
-------------------
<topaz:permissions>
</pre></p> Mulgara - Bug #188 (New): Zipped N3 files not recognized when loadinghttps://code.mulgara.org/issues/1882009-06-26T01:42:29ZPaula Gearon
<p>Loading a zipped N3 file successfully unzips the file, but doesn't recognize the extension as referring to an N3 file. As a result, the system falls back to the RDF/XML content handler, which naturally fails.</p>
<p>This should be fixable if the content handler starts looking for .n3.gz as well as .n3.</p> Mulgara - Bug #182 (New): Missing Link from http://localhost:8080/webservices/ to http://localhos...https://code.mulgara.org/issues/1822009-02-13T12:53:35Zben hysell -benh@viewpointusa.com
<p>Was looking for a link to the wsdl files on the webserver and could not find it by just browsing the website. Was able to find the link:</p>
<p><a class="external" href="http://localhost:8080/webservices/services">http://localhost:8080/webservices/services</a></p>
<p>by examining log files.</p>
<p>Would be nice to have a link on <a class="external" href="http://localhost:8080/webservices/">http://localhost:8080/webservices/</a> to <a class="external" href="http://localhost:8080/webservices/services">http://localhost:8080/webservices/services</a></p> Mulgara - Feature #178 (New): Queries with limits should be annotated as suchhttps://code.mulgara.org/issues/1782009-01-28T19:18:32ZPaula Gearon
<p>Some queries should have the limits applied while being processed via the FILTER operator. This is hard to apply in the general case, but if processing is being done at the level of the top conjunction or disjunction, then the limit can be applied to avoid latter processing.</p>
<p>An example is shown here in SPARQL:<br /><pre>
This requires processing of every line before returning the first one.</p></pre> Mulgara - Feature #171 (New): Default graph option to movehttps://code.mulgara.org/issues/1712008-11-18T20:40:25ZPaula Gearon
<p>Currently the SPARQL interpreter handles default graphs by setting the graph on any queries it parses.</p>
<p>A mechanism that will fit in better with the SPARQL protocol will be to allow the graph to be set to null, and for the Connection to set the graph. This will require all Connection implementations to accept a default graph setting, and to set this on any queries that require it as they are passed along the connection.</p> Mulgara - Bug #164 (New): Timer no longer workinghttps://code.mulgara.org/issues/1642008-11-04T15:32:47ZPaula Gearon
<p>The "set time on" command is no longer working, apparently since the Command interface was introduced.</p>
<p>This is to be implemented on the client side.</p> Mulgara - Feature #147 (New): Configurationhttps://code.mulgara.org/issues/1472008-09-08T18:15:06ZPaula Gearon
<p>Create a registry object for EmbeddedMulgaraServer to set pass out to any services that it starts up.</p>
<p>I was initially tempted to go with a dictionary, but I prefer the idea of keeping a tighter control on the information passed around. We can always expand what's held in the registry, but it will be centralized, rather than having services work on an ad hoc basis.</p>
<p>The reason this needs to be a registry and not a set of parameters is because objects may need to be passed to services after they have been created. The canonical example here is where the framework creates a SessionFactoryFactory, along with the web servlets, but until the startup phase there is no instance of Database - which is what the web servlets need. For the moment, each service is holding a handle to EmbeddedMulgaraServer and queries that object directly, but the internals of this class need to be kept away from all the objects it creates.</p> Mulgara - Bug #135 (New): Mulgara keeps file lock if parsing of RDF/XML failshttps://code.mulgara.org/issues/1352008-07-29T20:48:41ZAlex Hall -alexhall@revelytix.com
<p>Running Mulgara 2.0.0 on Windows XP, if the parsing of an RDF/XML file fails due to illegal content during a load, Mulgara does not release the lock on that file.</p> Mulgara - Bug #134 (New): Jar files contain duplicateshttps://code.mulgara.org/issues/1342008-07-24T22:17:10ZPaula Gearon
<p>There are multiple occurrences of several files in the distribution jars. For instance, grepping for the Castor generated file Jetty:<br /><pre>
$ jar tf mulgara-2.0.0.jar | grep 'Jetty\.class'
org/mulgara/config/Jetty.class
org/mulgara/config/Jetty.class
org/mulgara/config/Jetty.class
org/mulgara/config/Jetty.class
org/mulgara/config/Jetty.class
</pre></p>
<p>The final jars are built out of several sub-jars, which is where the duplicates come from. These duplicates need to be removed.</p> Mulgara - Feature #119 (New): URI/IRI deconflationhttps://code.mulgara.org/issues/1192008-05-17T23:08:38ZPaula Gearon
<p>Audit SPARQL to ensure that only valid IRIs are being used. This is mostly the case, as IRIs are a subset of URI.</p> Mulgara - Feature #27 (New): Eliminate all use of static variables from Mulgarahttps://code.mulgara.org/issues/272006-10-16T07:13:57ZAndrae Muys -andrae@netymon.com
<pre>
<code class="html syntaxhl">The use of static (ie. global) variables prevents Mulgara being restarted within a jvm. These are not necessary, and are being used to avoid considering where objects belong within the system.
<span class="nt"><br/></span>
<span class="nt"><br/></span>
Note this does not apply to static *constants* - being compile-time immutable values they are not an issue.
</code></pre>