Persistent Data For Essential Viewer

Post Reply
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

The data should be persistent in Essential Viewer. A snapshot of your repository is saved as an XML document in the Viewer web application.

If JBoss is re-deploying Essential Viewer on start up, then that will reset the repository XML snapshot. Normally, e.g. on Tomcat, once the application is deployed, the app server does not re-deploy and the data persists over a restart.

I would expect JBoss only to re-deploy the application if the WAR file has changed. Is there a configuration for JBoss that you can set to make it only redeploy if the WAR is newer than the deployed folder?

You do need to explicitly save any work in Protege if you are using the simple file-based backend for the repository. Assuming you're doing that, you can get the Viewer content back by re-publishing to Essential Viewer

Jonathan
Essential Project Team
Post Reply