Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] protege jar startup

Daniel Goergen daniel.goergen at biotronik.com
Thu Jan 11 03:04:26 PST 2007


Hi again,

i case someone has the same problem, I found the solution for web 
applications.
if you want to set the plugin and logging dir you have to set 

java -Dprotege.dir=/tmp/someDir

as jvm argument for the server application. 
(see details below)

greets

Daniel

> > is there any configuration possibility for the startup process? eg. 
not 
> > allowing plugins to load? 
> > 
> There is a way to mislead Protege :) You can set a jvm argument 
> "protege.dir" to another directory. Protege uses the protege.dir in 
> order to find the plugins directory and the protege.properties (and 
> other configuration files).
> 
> You can set the protege.dir for a standalone application like this:
> 
> java -Dprotege.dir=/tmp/someDir edu.stanford.smi.protege.Application
> 
> I am not sure how you can set this for a web application.
> 
> Then protege will try to find the plugins directory in 
> /tmp/someDir/plugins and it won't be able to find it, so it won't load 
> any plugins.
> Of course you create in /tmp/someDir a plugins directory in which you 
> add only the plugins you really want to load.
> 
> There is another small issue. In the current version, the Protege logger 

> will try to write the logs in the logs subdirectory of protege.dir. And 
> because it won't be able to, you will see some warnings in the console. 
> So, you could create in the protege.dir a logs directory. It is a good 
> idea to have the logs, in case you get some error from Protege and you 
> want to see what happened.



More information about the protege-discussion mailing list