I am using Fuseki from jena-fuseki-0.2.2-incubating-20120509.202022-18-distribution.zip in conjunction with SPARQLPuSH [1]. So far, most of my difficulties surround providing the right details of the queries when constructed by the the PHP that implements SPARQLPusH. My debugging life would be much easier if I could get fuseki to reveal the queries it receives via http, both post and get, before logging its response.
Is there a way to force this? Use case: Right now my debugging tends to take the form of figuring out where in the PHP app the query is constructed, making that point log to the apache server supporting the PHP, grabbing the query there and putting it into the fuseki web query form, and hoping that the error reported corresponds reasonably to the one signalled by fuseki when started in a Linux shell. I'd rather see those hints coming out of Fuseki before I dig into the calling code. Otherwise, I am hopping back and forth between my own Apache server logs and the reports Fuseki makes of its issues with my queries. Ideally, I'd be able to optionally see the query url-decoded, since the url-encoding library of most(?) application languages is rarely(?) problematic. Thanks Bob Morris [1] http://code.google.com/p/sparqlpush/ -- Robert A. Morris Emeritus Professor of Computer Science UMASS-Boston 100 Morrissey Blvd Boston, MA 02125-3390 IT Staff Filtered Push Project Harvard University Herbaria Harvard University email: [email protected] web: http://efg.cs.umb.edu/ web: http://etaxonomy.org/mw/FilteredPush http://www.cs.umb.edu/~ram === The content of this communication is made entirely on my own behalf and in no way should be deemed to express official positions of The University of Massachusetts at Boston or Harvard University.
