I think there is a discrepancy between jtds documentation and
implementation. Where they suggest to use
jdbc:jtds:microsoft://host[:port][/database] as the JDBC URI format,
it actually works if you enter
jdbc:jtds:microsoft://host[:port][/database]
But the problem presents itself in another way
Which one should I use...
On Nov 11, 1:38 pm, Holger Knublauch [EMAIL PROTECTED] wrote:
James,
we don't support AG 3.1 yet - it was published after TBC 2.6.2 came out.
Holger
On Nov 11, 2008, at 10:36 AM, jlapalme wrote:
This is the output of the Allegro console when I start it :
3.0
On Nov 11, 2008, at 10:45 AM, jlapalme wrote:
Which one should I use...
On Nov 11, 1:38 pm, Holger Knublauch [EMAIL PROTECTED] wrote:
James,
we don't support AG 3.1 yet - it was published after TBC 2.6.2 came
out.
Holger
On Nov 11, 2008, at 10:36 AM, jlapalme wrote:
This
Possibly the model did not have any imports or no classes? Please
check the Triples View to verify that it is indeed empty and report
your findings. Thanks!
Holger
On Nov 11, 2008, at 3:14 PM, Parsa Mirhaji wrote:
YES! That did the trick! It now But, I can’t see anything that is
there
Parsa; Good to get through the first step! Tale a look at the
Triples tab to see if Composer can see any of the triples in the
model. ...or let us know what can't be seen (the class hierarchy,
rdfs:Resource instances, etc.)
-- Scott
On Nov 11, 5:14 pm, Parsa Mirhaji [EMAIL PROTECTED] wrote:
Parsa; The model name is whatever you entered for Internal Jena
model name. If that isn't matching what you are looking for in the
database, then you will probably get a blank RDF file. I.e. you may
have created a file named with the single space you entered. And the
symptoms you state
