Re: [Lenyacms-dev] Publishing does not work anymore

Hi Lenya developers,

Michael Wechner wrote:
> Michael Wechner wrote:
> 
>> Michael Wechner wrote:
>>
>>> Hi
>>>
>>> It seems like that Publishing doesn't work anymore.
>>>
>>> The PublshingEnvironment class does not receive the correct
>>> publicationPath anymore. The first "/" is missing from the path,
>>> and hence is interpreted as a relative path and is appended (by 
>>> Avalon I guess) to the location from where the servlet engine has 
>>> been started.
>>>
>>> Has that anything to do with the introduction of some new classes from
>>> the end of last week
>>
>>
>> The error already seems to be done with the logicsheet util.xsl which 
>> is initializing the class
>> org.lenya.cms.publication.Publication, which is then calling the class 
>> Publishing Enviroment.
>>
>> It seems like the first slash is replaced by nothing ...
> 
> ok, it seems to be fixed now. There were two problems:
> 
> util.xsl:
> The logicsheet was removing the slash at the beginning. I guess Windows 
> is having 2, but Linux has only 1.

I altered the logicsheet, probably I was not careful
enough. There were some problems before my changes,
I have to look at it again. The publishing classes
contain a lot of string manipulation code, maybe I can
replace some of that with file handling code.

> xslt/publishing/main.xsl (resp. DefaultFilePublisher):
> The paramater "sources" was renamed to "properties.publish.sources"
> which threw an exception within the DefaultFilePublisher.

I'm sorry, that is my fault. I changed the main.xsl to
try out the AntTask-based publishing task and accidentially
checked it in.

> If you update your CVS, then you should probably make a clean 
> installation, because otherwise the fixed logicsheet might not be reloaded.

You have to delete the XSP java and class files from tomcat/work
and restart Tomcat.

> Well, we definitely have to introduce "the tests".

Yes, absolutely. It's hard to predict all influences
of a code change.

Again, sorry for the problems and thanks, Michael, for
the tracing and repairing!

Andreas