Ah, this is a known bug in that particular D2RQ version. They have thankfully fixed it and the new version will be part of the upcoming TBC release. As far as I remember there is a work-around (it had to do with the way that foreign keys are handled). I think you can modify the mapping file to prevent this error from happening. You may want to ask the D2RQ mailing list for details. Or just wait for the next release.
Holger On Oct 9, 2009, at 6:29 AM, Chris wrote: > > > The mappings appear to be OK from what I can tell after cleaning out > all of the > unnecessary entries. I should have been paying more attention to the > import error log > when loading the x-Test.owl file. > > The exception from the 'Failed to import' entry: > > java.lang.ClassCastException: de.fuberlin.wiwiss.d2rq.sql.ResultRow$1 > cannot be cast to com.hp.hpl.jena.graph.Triple > at org.topbraid.core.graph.CachingGraph.addToCache(CachingGraph.java: > 213) > at org.topbraid.core.graph.CachingGraph.find(CachingGraph.java:306) > at org.topbraid.core.graph.CachingGraph.find(CachingGraph.java:297) > at org.topbraid.core.graph.CachingGraph.rebuildCache > (CachingGraph.java:472) > at org.topbraid.core.registry.impl.GraphRegistry.register > (GraphRegistry.java:277) > at org.topbraidcomposer.core.io.TBCIO.loadModel(Unknown Source) > at org.topbraidcomposer.core.io.TBCIO.loadImportedModels(Unknown > Source) > at org.topbraidcomposer.core.io.TBCIO.loadImportedModels(Unknown > Source) > at org.topbraidcomposer.core.io.TBCIO$1$1.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > > Is this telling me that TBC is having trouble loading or that D2RQ is > having trouble > with the data itself? How might I track down exactly where in the > process that > it's bombing out? Are there detailed logs I can turn on somewhere in > TBC? > > > Thanks, > Chris > > > On Oct 7, 12:08 pm, Scott Henninger <[email protected]> > wrote: >> Chris; the .owlinf file will store the inference graph if you choose >> to do that. The -Test.owl file will hold the instance data from the >> RDB. >> >> If the mappings aren't quite right, you can modify the mapping model. >> >> -- Scott >> >> On Oct 7, 10:59 am, Chris W <[email protected]> wrote: >> >>> Per Scott's suggestion to David in an earlier post, I'm trying out >>> the >>> D2RQ/jTDS/SQLServer config. The import seems to go well. I see the >>> proper d2rq, mapping, schema, and test files; they contain proper >>> ontologies for the database that I'm connecting to. However, an >>> xxx- >>> Test.owl.owlinf is never generated and it doesn't appear to be >>> querying the database for instances of the classes when I go look >>> for >>> those. >> >>> Just to test the data, I exported everything to MySQL using the >>> MySQL >>> Migration Tool which works like a charm, BTW. Highly recommended. >>> Found that >>> athttp://stackoverflow.com/questions/129/how-to-export-data-from-sql-se >>> .... >>> I ran the D2RQ import on that with JDBC and all is well. >> >>> So I have a working solution, but I'd really like to figure out >>> how to >>> talk to that native SQL Server DB. I realize this is very likely >>> not >>> a TBC problem, per se, but the experts seem to be here, so I thought >>> I'd post the issue. Any suggestions on where I could troubleshoot? >>> User/passwd that I'm using is the database owner, and it's getting >>> the >>> database tables info, so it doesn't seem to be a connection problem. >>> Could it just be a SQL Server glitch? An issue with the jTDS >>> driver? >> >>> Thanks, >>> Chris >> >> > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
