cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <>
Subject Re: ForrestBot build for cocoon-docs FAILED
Date Fri, 05 May 2006 15:50:14 GMT
On Fri, 2006-05-05 at 16:28 +0100, Ross Gardler wrote:
> wrote:
> > Automated build for cocoon-docs FAILED
> ...
> >      [java] X [0]                                     2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.TreeModel
BROKEN: No pipeline matched request: 2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.TreeModel
> >      [java] X [0]                                     2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.Tree
BROKEN: No pipeline matched request: 2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.Tree
> >      [java] X [0]                                     2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.TreeWalker
BROKEN: No pipeline matched request: 2.1/userdocs/widgets/javadoc:org.apache.cocoon.forms.formmodel.tree.TreeWalker
> This looks like someone has used a javadoc: protocol in the source 
> files. Unfortunately, Daisy does not recognise
> We can see which pages contain these broken links by lookig at:
> That leads us to:
> from where we can get to the Daisy source page by following the edit 
> link at the bottom of the page:
> In this document we can see that daisy is using a pseudo protocol of 
> "javadoc:". This protocol is not processed by Daisy when publiching the 
> XML version of the document, and Forrest knows nothing of this 
> pseudo-protocol.
> However, all is not lost. I recall reading on the Daisy dev list that it 
> uses Forrests locationmap code to handle psuedo protocols like this. if 
> someone can point me at how this is done within Daisy I'll look at 
> making the forrest publication honour the protocol. Alternatively, we 
> need the XML source to contain the URI that this resolves to.

Oops! I knew there was some reason I couldn't use this feature yet, but
had forgotten about it.

Below is the information about how it is configured. If it would be too
inconvenient to add it to forrest right now, I can remove the usages of
"javadoc:" in the document itself (though its *very* handy).

The link transformer is configured like this:

    <map:transformer logger="sitemap.transformer.linkrewriter"
      pool-grow="2" pool-max="32" pool-min="2"

In cocoon.xconf this input module is defined:

    <component-instance name="javadoc"
      <file src="context://daisy/javadoc_locationmap.xml"/>

and the javadoc_locationmap.xml file is attached.

Bruno Dumon                   
Outerthought - Open Source, Java & XML Competence Support Center                

View raw message