Paul,
As Holger stated, we will internally discuss later how the we would have
or not have support for Sesame 2.6 in the next TBC release. Most likely
we won't support pre-2.6 and 2.6 connectors simultaneously, but support
at least one of them.
Gokhan
On 11/11/2011 1:48 AM, PaulZH wrote:
Some additional context.
Since new versions of OWLIM come with the latest sesame built-in the
problem isn't limited to sesame alone.
Paul
On Nov 11, 10:39 am, PaulZH<[email protected]> wrote:
Isn't it possible to foresee two connectors:
- pre-2.6
- 2.6
This should avoid the need for all users to upgrade.
Paul
On Nov 11, 2:37 am, Peter Ansell<[email protected]> wrote:
The change was made to fix a known replicable bug, so it will be
necessary to support binary format version 4 in the long term. The
database upgrade may be smooth, as the fix was made to the format, and
not to the underlying database structure as far as I can tell.
The main new feature of Sesame 2.6.0 was SPARQL 1.1 Federated Query,
so it may also depend on whether people want that feature. They may
also want the new SPARQLRepository interface that was ported down from
Alibaba into Sesame Core to support federated querying.
In addition, I doubt that fixes for SPARQL 1.1 bugs will be backported
to the Sesame 2.5 series, but it is possible.
http://www.openrdf.org/issues/browse/SES-741
http://www.openrdf.org/issues/browse/SES-832
Cheers,
Peter
On 11 November 2011 11:06, Holger Knublauch<[email protected]> wrote:
Thanks for the info. I guess we need further internal discussions as to whether
we want (and can afford) to upgrade to Sesame 2.6 before we can promise any
change for 3.6. For example it would force all existing users to upgrade their
databases.
Holger
On Nov 11, 2011, at 8:52 AM, Peter Ansell wrote:
There was a post like this on the Sesame mailing list recently [1].
The Sesame Binary RDF format changed between 2.5 and 2.6 [2].
HTH,
Peter
http://sourceforge.net/mailarchive/forum.php?thread_name=4EA7086D.804...
http://www.openrdf.org/issues/browse/SES-852
On 11 November 2011 07:29, Bob Ducharme<[email protected]> wrote:
Paul,
One of our engineers has confirmed that TopBraid 3.5.2 works properly with
Sesame 2.5.1, and he got the same error that you did when he tried it with
Sesame 2.6. I have entered a bug report to ensure that TopBraid 3.6 works
properly with Sesame 2.6.
Bob
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of PaulZH
Sent: Thursday, November 10, 2011 8:27 AM
To: TopBraid Suite Users
Subject: [topbraid-users] connecting with openrdf sesame 2.6
Dear,
When trying to open a Sesame2 Repository Connection with a sesame
updated to version 2.6 I get:
Reason:
org.openrdf.repository.RepositoryException: Malformed query result
from server
at
org.openrdf.http.client.HTTPClient.getTupleQueryResult(HTTPClient.java:
971)
at
org.openrdf.http.client.HTTPClient.getRepositoryList(HTTPClient.java:
371)
at
org.openrdf.http.client.HTTPClient.getRepositoryList(HTTPClient.java:
353)
at
org.topbraid.sesame2.SesameUtil.getRepositoryNames(SesameUtil.java:
85)
at
org.topbraidcomposer.sesame2.remote.AbstractSesameRemoteWizardPage.handleFet
ch(AbstractSesameRemoteWizardPage.java:
146)
at
org.topbraidcomposer.sesame2.remote.AbstractSesameRemoteWizardPage.access
$0(AbstractSesameRemoteWizardPage.java:142)
at
org.topbraidcomposer.sesame2.remote.AbstractSesameRemoteWizardPage
$1.widgetSelected(AbstractSesameRemoteWizardPage.java:100)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
3622)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at
org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcu
tAction.java:
135)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Action
ContributionItem.java:
584)
at org.eclipse.jface.action.ActionContributionItem.access
$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem
$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
3622)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3277)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2629)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:
332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
663)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.
java:
115)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:
196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
EclipseAppLauncher.java:
110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAp
pLauncher.java:
79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
369)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: org.openrdf.query.resultio.QueryResultParseException:
Incompatible format version: 4
at
org.openrdf.query.resultio.binary.BinaryQueryResultParser.parse(BinaryQueryR
esultParser.java:
118)
at
org.openrdf.http.client.HTTPClient.getTupleQueryResult(HTTPClient.java:
965)
... 50 more
Going back to the 2.5 wars solves the issue.
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
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-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
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-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
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-users?hl=en
--
You received this message because you are subscribed to the Google
Group
...
read more ยป
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
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-users?hl=en
