...and I see that my post is also not relevant as you state you are using TBC-ME localhost (hence no Live/Tomcat).
There are currently some issues with opening Sesame repositories that are not created by Composer. We are investigating this. In the meantime, a possible work-around is to read the repository into Composer (TDB can be used if the repository is too large for memory), then use export to write to Sesame. Composer will be able to open the resulting repository and you will see the triples is stores. -- Scott On Oct 12, 4:10 am, PaulZH <[email protected]> wrote: > Scott, > > I discovered that this error message is not relevant for the issue. > > Paul > > > > > Your log does indicate that thee may be a connection problem. Perhaps > > looking at the Tomcat (I'm assuming that is your servlet container) > > logs for Sesame will provide some more information? > > > -- Scott > > > On Oct 5, 5:02 am, PaulZH <[email protected]> wrote: > > > > Did find error message. > > > > Error > > > Mon Oct 05 11:44:09 CEST 2009 > > > Could not connect to Sesame repository > > > org.openrdf.repository.http.httpreposit...@1af1ad8 > > > > org.openrdf.repository.RepositoryException: java.net.ConnectException: > > > Connection refused > > > at org.openrdf.repository.http.HTTPRepositoryConnection.getNamespaces > > > (HTTPRepositoryConnection.java:304) > > > at org.topbraid.sesame2.graph.RepositoryGraph.initNamespaces(Unknown > > > Source) > > > at org.topbraid.sesame2.graph.RepositoryGraph.<init>(Unknown Source) > > > at > > > org.topbraid.sesame2.module.importSesameRemoteRepository.ImportSesameRemoteRepositoryModule.getRDFOutput > > > (Unknown Source) > > > at org.topbraid.sparqlmotion.engine.impl.ExecutionEngine.executeModule > > > (Unknown Source) > > > at org.topbraid.sparqlmotion.engine.impl.ExecutionEngine.execute > > > (Unknown Source) > > > at org.topbraid.sparqlmotion.util.AbstractSMGraphStore.getGraph > > > (Unknown Source) > > > at org.topbraid.sparqlmotion.util.AbstractSMGraphStore.getBaseURI > > > (Unknown Source) > > > > Paul > > > > On Oct 5, 11:31 am, PaulZH <[email protected]> wrote: > > > > > Having successfully Sesame 2.2.4 running on localhost. > > > > Created a repository, loaded some triples which I can see and query in > > > > the Sesame Workbench. > > > > > Connecting now from TBC-ME 3.1.1 using the wizard. > > > > Using Sesame's service URL I'm able to fetch the list of repositories, > > > > so I think the connection works. > > > > Choosing a repository then opens TBC, but no custom triples to be seen > > > > or found. > > > > > A similar issue was reported by James A Miller end of May, but I was > > > > not able to find more info. > > > > > >I am able to successfully connect to the Sesame 2 remote repository, > > > > >but > > > > >I don't see triples. I don't get any error messages. I was able > > > > >to Fetch Repositories successfully--my store was in the list. > > > > >I ran a SELECT * WHERE {?a ?b ?c} query, and I get results--but only > > > > >the > > > > >standard OWL, RDF, XSD triples: none of my 'custom' triples that I > > > > >see > > > > >in the Sesame workbench. > > > > > Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
