cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject entity resolution for Documentation build - almost
Date Mon, 01 Oct 2001 13:55:20 GMT
I have started adding to the "newdocs" target of build.xml
to copy the entities and system catalog to the build space.
This does work and the entity resolver swings into action.

However, i get a strange failure when i declare an external
entity in my xdocs. The only difference that i can spot is that
the system identifier ends up starting with "file://" using the
command-line cocoon-based build of "newdocs". Yet when
using the servlet context (e.g. via cocoon samples) the system
identifier ends up starting with "file:/" (and all is OK with the

The second double slash in the URL is from the getRealPath()
method. This also does not happen via the servlet context.
Instead there is a proper single slash.

Here is the log snippet ...
DEBUG   10019   [        ] (): SAXParser: 

Resolved public: ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML 

Failed to create InputSource: 

DEBUG   10019   [        ] (): ComponentFactory decommissioning
instance of org.apache.cocoon.components.parser.JaxpParser.

On Fri 28 Sep 2001, Carsten Ziegeler wrote:
> Hi Team,
> due to some lack of time, I just checked-in a very earlier
> and ugly version of the documentation system. I checked
> in only into the head of the cvs.
> It's based on the avalon solution and uses the cli of
> cocoon to build the docs.
> The build target is "newdocs", all files are located
> in the documentation directory.
> There you find a sitemap, some stylesheets and all xdocs.
> I started to outline the docs to the proposal from Berin
> but didn't come very far...
> What has to be done:
> - Totally missing is the image generation for the labels.
>   I started some svg tests (a starting point is the
>   svg directory in the documentation directory).
> - All documentation has to be entered at two places:
>   the book.xml for describing the documentation outline
>   and the *.uris files which are used as input to c2
>   to build the docs.
>   I think we should unify this and generate from the
>   book.xml a *.uris file
> - The stylesheets currently do not cover all areas.
> ....
> So just play a little bit with it and enhance it, please.
> And if you think: "Oh my, that's crap" just change it
> the way you want.
> Carsten

To unsubscribe, e-mail:
For additional commands, email:

View raw message