Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (athena.apache.org: domain of scherler@gmail.com designates
 74.125.82.179 as permitted sender)
Message-ID: <4F723BAE.2060900@gmail.com>
Date: Wed, 28 Mar 2012 00:14:06 +0200
From: Thorsten Scherler <scherler@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: c3: null pointer exception in
 ResponseHeaderCollector.isModifiedResponse
References: <4F6CD848.9000400@sil.org> <4F708060.103@sil.org>
 <4F7081FC.6040302@apache.org> <4F709D91.6060601@gmail.com>
 <4F720B4B.2030405@sil.org>
In-Reply-To: <4F720B4B.2030405@sil.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 03/27/2012 08:47 PM, Lars Huttar wrote:
> Thorsten wrote,
>
>> Hmm, did actually somebody tried c3 on win before?
>>
>> I just downloaded the file on a pet project I have and it works 
>> without any prob on linux.
>>
>> So let us do the clean routine: cd $c3_home svn up mvn clean install 
>> cd /c3/theParent mvn clean install cd ethnologue-17-pub/ mvn jetty:run
>>
>> Does the error persists? I can remember i came in contact with 
>> DataStore, when I created a jms based pipe and did not enter a c3 
>> context, but this is not your case at all.
>>
>
> I don't actually have a $c3_home envt variable - maybe that was just 
> shorthand? I did a svn up in c:\Program Files\Apache Software 
> Foundation\c3, which is *a* place that I installed C3. I may have 
> installed it in more than one place, and if so, I don't know which 
> place is the relevant one. Is there any way to find out? I also did 
> mvn clean install in that directory.
>
> Then I went to theParent (which is not under the folder where I did 
> svn up) and did
> mvn clean install
> cd ethnologue-17-pub
> mvn jetty:run
>
> Yes, the error persists. I get this in the cocoon.log:
>
> ...

Javier wrote this morning something that he was on a vm windows and 
could reproduce the problem. Need to talk to him when he comes into 
work. Further I will ask our intern to try on windows. Really seems to 
be a problem with windows. Will keep you informed.

salu2

-- 
Thorsten Scherler<scherler.at.gmail.com>
codeBusters S.L. - web based systems
<consulting, training and solutions>

http://www.codebusters.es/