At 03:10 PM 8/29/2000 -0700, christopher baus wrote:
>At 07:39 PM 8/23/2000 -0700, Jon Stevens wrote:
>>on 8/23/2000 7:31 PM, "Travis Low" <[EMAIL PROTECTED]> wrote:
>>
>> > In the zone repository, alas.  The hoster is willing put it into the
>> > wrapper.classpath, but it requires a server restart and therefore must be
>> > scheduled.  Turnaround is a day or so, making testing difficult.
>>
>>I put everything that I have source code to into my zone.repo.
>>
>>-jon
>Ok now I'm having problems with ecs-1.3.3.jar in my zone repositories 
>propriety.  This seems to work fine on my Win32 setup, but not Linux. Yes 
>the jar is where the repository points to.  Are there known problems with 
>property parsing in jServ that I'm not familiar with.  This is getting 
>frustrating.  BTW, it works fine if I unzip the jar in the repository path.
>
>I get something like this in my error_log.
>
>Cannot find org.apache.ecs.ecs.properties.
>java.lang.ExceptionInInitializerError
>         at org.apache.jserv.JServConnection.processRequest(Compiled Code)
>         at org.apache.jserv.JServConnection.run(Compiled Code)
>         at java.lang.Thread.run(Compiled Code)
>java.lang.NoClassDefFoundError: org/apache/ecs/ECSDefaults
>         at org.apache.jserv.JServConnection.processRequest(Compiled Code)
>         at org.apache.jserv.JServConnection.run(Compiled Code)
>         at java.lang.Thread.run(Compiled Code)

The problem seems to be having the ecs.properties file in the jar file.  Is 
anyone else noticing this on jServ?  I can't seem to find it documented 
anywhere.




==========================================================
christopher baus                Come down off the cross,
waiting for snow                we could use the wood.
in Tahoe, NV                    -- Tom Waits.



------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to