hi richard,

well, you probably didn't find it, because your logging configuration seems
to be different (i.e. strange to me ;-). maybe that's normal for older
cocoon versions, I only know cocoon >= 2.0.3.

one issue (actually 3 ;-) I could find, which is an error in your
sitemap.xmap:


<!-- ========================== Soundpool
================================ -->

<pipelines>
 <pipeline>
        <map:match pattern="soundpool.xml">
                <map:generate src="soundpool.xml"/>
                <map:transform src="soundpool.xsl"/>
                <map:serialize type="html"/>
        </map:match>
 </pipelines>
</pipeline>

you tried to surround your single soundpool pipeline with a 'pipelines'
element. furthermore both are incorrectly nested (you should be editing with
an XML editor, which wouldn't allow this). third one: the namespace prefix
(map) on <pipeline> is missing.

so, this fragment should look like:

<map:pipeline>
        <map:match pattern="soundpool.xml">
                <map:generate src="soundpool.xml"/>
                <map:transform src="soundpool.xsl"/>
                <map:serialize type="html"/>
        </map:match>
</map:pipeline>


there could be other issues (I got errors when trying with 2.0.3), but that
maybe my setup. or it maybe a cocoon 2.0 thing, with which I couldn't really
help.


I'd really recommend upgrading to cocoon 2.0.4 and tomcat >= 4.0.6.

> -----Ursprungliche Nachricht-----
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Im
> Auftrag von Richard Cunliffe
> Gesendet: Mittwoch, 29. Januar 2003 01:19
> An: [EMAIL PROTECTED]
> Betreff: RE: I cant get cocoon to process??
>
>
> Marco,
>
> I have attached all the logs and my sitemap. I searched
> 'PreparableMatcher', but nothing came back.
>
> Thank you so much for taking a look at this for me!
>
> Richard.
>


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to