http://www.openrdf.org/issues This file is an XML representation of an issue en http://www.openrdf.org/issues/browse/SES-800 Method prepareQuery in HTTPRepositoryConnection throws UnsupportedOperationException() <br/> causes problem when connecting to a HTTPRepository, which itself is using a remote repository as store SES-800

Unimplemented/Unsupported method prepareQuery in org.openrdf.repository.http.HTTPRepositoryConnection

Improvement Major Resolved Fixed Jeen Broekstra Konstantin Pentchev Wed, 20 Jul 2011 15:01:10 +0200 (CEST) Wed, 24 Aug 2011 09:07:05 +0200 (CEST) 2.4.2 2.5.0 HTTPRepository 0 This is actually not a new problem in Sesame 2.4, but has always been implemented (or rather, not implemented) this way. <br/> <br/> prepareQuery is listed as an optional operation in the API, and in the HTTPRepository it's not implemented for performance-reasons: supporting this method requires determining the query type on the client side, which implies a parsing step. Not only is that expensive, but HTTPRepository currently has no dependency on the SPARQL parser. <br/> <br/> I guess we might be able to implement this using a regular expression though. Need to have a think about it. <br/> <br/> <br/> <br/> I have checked in an implementation for this method in HTTPRepositoryConnection, using regular expressions and some other string manipulation tricks, but I am not convinced it's foolproof (even though it passes a few unit tests I came up with), and it's probably not very efficient. I have updated the javadoc to stress that the preferred way of preparing queries is still to use the more specific prepareTuple/Boolean/GraphQuery methods. I would like some feedback from people on this fix before I mark it resolved.