On Tue, 6 Jun 2000, Sandor Szego wrote:
> I had experienced the same error. After debugging a while, I found that the
> properties in my TurbineResources.properties file were not read correctly (I
> mean: were not read as *I* expected them to be read:). In particular, I had
> problems with paths: e.g. (if my memory serves me), jetspeed.properties had
> the value
> /javalib/apache/Jetspeed-1.1/src/config/JetspeedResources.properties. This
> was interpreted as:
> http://[myhost]/javalib/apache/Jetspeed-1.1/src/config/JetspeedResources.pro
> perties. This of course did not work. My fix: I added the /javalib virtual
> path to my webserver. It works now.
Usually when specifying a relative path in a web server environment you
will get the this behavior.
I would NOT put my config directory accessible under the webserver
document directory, which seems to be what you did to fix the problem.
This is bad because people can just read your config file via the
webserver by opening the url.
http://[myhost]/javalib/apache/Jetspeed-1.1/src/config/JetspeedResources.properties
The real way to fix this is to specify an absolute path to the
JetspeedResources.properties file. Lets assume that javalib resides in
/usr/local directory in this case you should specify
jetspeed.properties=/usr/local/javalib/apache/Jetspeed-1.1/src/config/JetspeedResources.properties
in the turbine resources.properties.
If I am interpreting wrong and /javalib exists in the top level like
/home, /usr, and /etc we need to look into this behaviour...
Jeff Prickett
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
