Ryan,

I am currently using tomcat and build seperate .war files for different
versions of longwell. i.e. I have two version running now:
http://localhost:8080/longwell-2.4.1/
http://localhost:8080/longwell-2.4.2/
I am not using any relational database and use the file triple store(I
believe).

Now my previously saved information/bookmarks are saved in the database
folder in webapps/longwell-2.4.1/WEB-INF/.../database
I found if I simply copy this database folder to
webapps/longwell-2.4.2/WEB-INF/.../database. The previous bookmarks/tags
do not show up in the new version (longwell-2.4.2).

Both apps are on the same server but different folders. I orignally
intended to do an upgrade instead of keeping both versions running but I
am afraid the new version will overwrite the previously saved data. Please
let me know if there is a better way to upgrade.

btw, I tried the new version 2.4.2 on the same server and I can
save/publish to it from other clients. At the same time, I continue to see
the previous errors in version 2.4.1.

Thanks a lot.

-Jimmy

> I tried to copy the WEB-INF/database from 2.4.1 folder to 2.4.2 folder but
> it didn't pass all the previous data to the new version. I found some
> instructions on upgrading from semantic-bank to longwell but didn't find
> instructions regarding longwell's upgrade. Is there an easy way to upgrade
> from 2.4.1 to 2.4.2?

There's nothing different between versions that would require you to
update data; we didn't change anything regarding the Sesame backend.

Migrating data from one place to another is a separate question.  What
do you mean by 'it didn't pass all the previous data?'  What's missing?

-- 
Ryan Lee                  [EMAIL PROTECTED]
MIT CSAIL Research Staff  +1.617.253.5327
http://simile.mit.edu/
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general



_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general

Reply via email to