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] Server problem and Ontology list won't display

Natsuda Kasisopha gift8201 at
Fri Oct 2 05:16:19 PDT 2009

Dear Jennifer,

Sorry for the confusion and frustration on my problem. I'm no different 
from you. You were talking about the URL of my web site 
"" and how did the 
"webprotege" didn't appears on the URL, the URL of 
""  is another alias that 
equivalence to "http://localhost:8080/webprotege/" but different host 
name. If you put 
it would appear Error message "HTTP Status 404  - 
/webprotege/webprotege/WebProtege.html". This has shown that the URL 
"" already pointing to  
"webapps/webprotege/WebProtege.html" just like  
"http://localhost:8080/webprotege/" path.

On your request of how am I deployed the Web Protege on the server. 
First of all, I'm using a shared server (host) name 
"" of the institute that I am studying at. I 
access the server remotely by using winSCP. I don't have the direct 
access to the server. According to your instruction and the instruction 
in the wiki, the Tomcat suppose to unzip the "webprotege.war" 
automatically but the winSCP doesn't do that. Thus I unzip the file on 
my computer and then upload them to the server. The directory path on 
the server, the server administrator manage and provide for me. I'm only 
allow to modify/delete the content in webprotege folder.

I notice in the log file i sent you. There were a fill Warning about the 
"plugins" directory, please refer to the message below. Is this 
directory need for the Web Protege page?
WARNING: Plugins directory not found: 
30-Sep-2009 13:57:39 edu.stanford.smi.protege.resource.BundleHelper <init>

WARNING: Plugins directory not found: 
30-Sep-2009 13:57:39 edu.stanford.smi.protege.resource.BundleHelper <init>

I hope the information I give would help.

Jennifer Vendetti wrote:
> Hello Natsuda,
> We are trying to reproduce your problem here, but have been 
> unsuccessful so far.  One question we have is how you managed to 
> configure your server such that there is no "webprotege" in the path 
> to the WebProtege application.  In other words, you sent us the URL of 
> "", which launches 
> WebProtege.  But, if we run WebProtege using the standard way of 
> deploying the WAR file to Tomcat, we end up with a URL that looks like 
> this: http://localhost:8080/webprotege/.  One possibility is that the 
> aliases that your admin has set up is somehow preventing WebProtege 
> from finding the projects that are listed in the metaproject.  But, we 
> are having trouble reproducing your particular deployment scenario.  
> Are there any more details you can give us about how you set up your 
> deployment - in particular, how did you eliminate the "webprotege" 
> portion of the path?
> Jennifer

More information about the protege-discussion mailing list