forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: The Mythical Javadoc generator (Re: Conflict resolution)
Date Fri, 13 Dec 2002 17:23:48 GMT
On Fri, Dec 13, 2002 at 05:45:11PM +0100, Steven Noels wrote:
> Jeff Turner wrote:
> >So assuming that the javadocs are already in build/site/apidocs, how do
> >we handle <link href="java:org.apache.Blah">.
> >
> >Seems the simplest approach is to just strip it from the links view of
> >the resource, so Cocoon doesn't even see it.
> If that assumption is true and the Transformer is/can be configured 
> accordingly: yes.
> >That's what my patch did for 'file:' URLs.
> It ain't me who asked to revert it ;-)
> I had my doubts whether XSLT was the way to do it, though.

There are some schemes which can't be done in XSLT:

- mail:<Message-Id> being transformed into a URL for marc.theaimsgroup or
- linkmap:<link XPath>, which requires opening linkmap.xml.  I currently
  have a half-written transformer written for this.  But even querying
  linkmap.xml could be done with XSLT, using the EXSLT dynamic XPath
  extensions that most processors implement.

How would a single configurable transformer be able to do all this?
Wouldn't having a transformer per scheme be easiest?  Then users can add
their own by editing the sitemap.


> I'm sure we can come up with a decent set of 
> link-rewriting/-resolution/view-bypassing rules, so that everybody gets 
> what he wants. If that involves view bypassing for static resources: why 
> not. I know I'll be using that one.
> </Steven>
> -- 
> Steven Noels                  
> Outerthought - Open Source, Java & XML Competence Support Center
> Read my weblog at    
> stevenn at                stevenn at

View raw message