Search Mailing List Archives
[protege-discussion] Fwd: WebProtege
matthew.horridge at cs.man.ac.uk
Mon Nov 12 18:49:02 PST 2012
Yes, this is a fair warning. So, be warned! :)
In particular, the back end format *will* change in the near future - there's a chance the old format will still work, but we won't promise this. We are also revising some of the core data structures - so expect to have to make some changes for any front end stuff you're developing as well.
On 12 Nov 2012, at 14:22, Tania Tudorache wrote:
> OK, your risk :) We warned you :)
> You will still need to include the libs that are documented on the wiki that depend on Protege 3 because we have both backends still in place. We are gradually cleaning up the code, and these dependencies will be gone eventually. Try to include all the jars you find, including the ones in WEB-INF/lib. It should at least compile.
> The new OWL server is not working with WebProtege, yet. Currently it uses a different mechanism and a binary (and super fast!) backend for storing the changes and supporting concurrency that Matthew implemented.
> In any case, we don't recommend that you do any development (at least backend side) with WebProtege 2.0 because we might change it significantly.
> Good luck!
> On 11/09/2012 08:09 PM, matthew lange wrote:
>> I don't mind hacking on the bleeding edge--can stick with what I have,
>> and be including libraries from the more recent OWL Protege Servers? I
>> am more interested in OWL compliance anyway...
>> On Fri, Nov 9, 2012 at 3:01 PM, Tania Tudorache <tudorache at stanford.edu> wrote:
>>> Hi Matthew,
>>> We have recently changed the location of SVN for WebProtege 1.0 (the one
>>> that works with Protege 3.x). This is the new SVN location that you should
>>> check out:
>>> Sorry, I thought I have updated the wiki description, but obviously, I
>>> haven't. I just did now..
>>> The SVN version will work also with the latest Protege 3.x release, so you
>>> can use newer versions of Protege 3.x. It also works with GWT 2.4.
>>> There is a newer version of WebProtege 2.0 that works with the OWL-API, and
>>> that has a reimplemented backend (which is what you have checked-out). That
>>> version is not yet ready for plugins or development, as we are still
>>> cleaning it up.
>>> Let us know if you still have problems.
>>> On 11/08/2012 11:51 PM, matthew lange wrote:
>>> I am getting a whole host of errors that I don't understand, including a
>>> fail to build in Eclipse.
>>> I am following the build instructions here. Upon attempting to build, I get
>>> the workspace build message:
>>> Building workspace has encountered a problem.
>>> Errors occurred during the build.
>>> Errors running builder 'Google App Engine Project Change Notifier' on
>>> project 'WebProtegeICF'.
>>> NO_MODIFICATION_ALLOWED_ERR: An attempt is made to modify an object where
>>> modifications are not allowed."
>>> Further errors are attached.
>>> I am using jars from protege 3.5.1 beta as instructed in linked webpage
>>> above. WebProtege is from trunk on SVN.
>>> All files except the junit jar are in my personal directory with read/write
>>> Thanks in advance for your help.
>>> protege-discussion mailing list
>>> protege-discussion at lists.stanford.edu
>>> Instructions for unsubscribing:
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
More information about the protege-discussion