I took a look at this earlier - and the pipeline Gaurav was attempting
to debug did not actually produce any output that could be serialized -
so there was nothing wrong with the set up or the very good instructions
on the wiki ; )


[email protected] wrote:
> More information would be helpful.
> What operating system?  (determines security and filepath limitations)
> What version of Lenya?  (for version-specific peculiarities that others know)
> What are your additions to the code:  (placement, typos, etc.)
> - in cocoon.xconf?
> - in an XMAP?
> solprovider
>
>
> On 1/6/09, Gaurav Kalia <[email protected]> wrote:
>   
>>  I have already created the folder named debug at that location.
>>  But the file is not getting generated in that folder.
>>
>>  Please suggest
>>  Thanks for Help
>>
>>  Regards
>>  Gaurav
>>
>>  Florent André wrote:
>>     
>>> if you copy-paste the code, you have this in the resource's code :
>>>       
>> <map:parameter name="source"
>> value="context://lenya/pubs/debug/{fileprefix}-{filedatetime:currentDate}.xml"/>
>>     
>>> This value define the folder where is write your file (where =
>>> lenya/pubs/debug in the Webapps/lenya/ folder) :
>>> * Have you create the folder debug in lenya/pubs ?
>>> * your lenya app have the write right in your folder ?
>>>
>>> Give some details if this suggest don't solve your problem.
>>>
>>> On Tue, 06 Jan 2009 19:56:13 +0530, Gaurav Kalia
>>> <[email protected]> wrote:
>>>       
>>>> Apropos of the link
>>>>         
>> http://wiki.apache.org/lenya/DebuggingTips
>>     
>>>> I am trying to debug sitemap by using the second method.
>>>> I have already configured everything according to the method.
>>>> And i am calling the resource in a particular pipeline that i want to
>>>> debug.
>>>> But still the log file is not getting generated.
>>>>
>>>> Please Suggest
>>>> Thanks for help
>>>> Gaurav
>>>>         


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to