Hi Pauline,
We've been trying to clean up how 4.0 deals with content/thredds. So, it
is good to hear 4.0 doesn't have the same problems 3.17 has on Jetty.
I'm also working on more flexibility for the location of the content
directory.
We haven't worked with Jetty but I would guess it should deal with
Apache authentication as well as Tomcat. I'm not as familiar with the
TDS restricted data access as John. He might have comments on that.
Ethan
Pauline Mak wrote:
> Hi all,
>
> I've installed the development version (4.0) on Jetty and it has
> detected the log4j config file correctly and has put everything in
> $JETTY_HOME/content/thredds!
>
> Cheers,
>
> -Pauline.
>
> Pauline Mak wrote:
>> Hi all,
>>
>> I've installed THREDDS on Jetty 6 and would like to find out if anyone
>> else has done the same. It worked mostly, except it was looking for
>> the config files in $JETTY_HOME/webapps/content/thredds. But on
>> Tomcat, it's in $CONTAINER_HOME/content/thredds. It's also having
>> difficulty finding the log4j config XML - it's looking for it in
>> /opt/jetty-6.1.15.rc4/webapps/threddsWEB-INF/log4j.xml. I'm guessing
>> something is not adding a separator in there...
>>
>> Apart from having to manually copy the initialContents directory into
>> $JETTY_HOME/webapps/content/thredds, the server installed without a
>> hitch :)
>>
>> I'm also planning to use Apache to handle authentication - so would I
>> be missing anything if I use Jetty instead of Tomcat?
>>
>> Cheers,
>>
>> -Pauline.
>>
>
>
--
Ethan R. Davis Telephone: (303) 497-8155
Software Engineer Fax: (303) 497-8690
UCAR Unidata Program Center E-mail: edavis@xxxxxxxx
P.O. Box 3000
Boulder, CO 80307-3000 http://www.unidata.ucar.edu/
---------------------------------------------------------------------------
