search

protegeproject / protege-server

An OWL ontology server for OWL API programs, e.g., Protege Desktop.
21 stars 16 forks source link

Remove the dependency of the protege-client on the protege-server #19

Open rsgoncalves opened 8 years ago

bdionne commented 7 years ago

This would be nice, but if anything we're moving in the opposite direction in terms of the client depending on server packages, .eg.

import org.protege.editor.owl.server.api.CommitBundle;
import org.protege.editor.owl.server.http.HTTPServer;
import org.protege.editor.owl.server.http.messages.EVSHistory;
import org.protege.editor.owl.server.http.messages.HttpAuthResponse;
import org.protege.editor.owl.server.http.messages.LoginCreds;
import org.protege.editor.owl.server.util.SnapShot;
import org.protege.editor.owl.server.versioning.VersionedOWLOntologyImpl;
import org.protege.editor.owl.server.versioning.api.ChangeHistory;
import org.protege.editor.owl.server.versioning.api.DocumentRevision;
import org.protege.editor.owl.server.versioning.api.ServerDocument;
import org.protege.editor.owl.server.versioning.api.VersionedOWLOntology;
import org.protege.editor.owl.server.versioning.api.HistoryFile;

@johardi and I discussed this a bit yesterday. Perhaps what's needed is to leave Protege-Client as is with all it's GUIs and carve out a small library that includes the LocalHttpClient, SessionRecorder, ClientSession, and the other bits needed to communicate with the server and manage commits to the ontology. In particular, EditTab, though it is bundled as a separate plugin, depends on ClientSession and thus is sensitive to the plugin load order, or lack thereof.