You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@sundn.de> on 2001/09/27 16:17:19 UTC
[C2]: Documentation System
Hi Team,
for the final release of C2 we should take some time and
update the documentation.
Several weeks ago, Berin made a very good proposal
for outlining the documentation
(see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
I think as we developed Cocoon we should also use
Cocoon to build the documentation!
The Avalon project shows how to do this. Now, I
just started to adapt the Avalon documentation
build system to ours. Making it really working
well and maintainable will be a more complex
effort than I thought it is.
So before I go any further, we should
vote on this topic.
So lets vote if we still should use stylebook
or we should "update" to Cocoon for docs
generation. Please note that this question
has nothing to do with the question of
the format the docs are written in!
That's a separate task!
Although it's a lot of work my vote:
+1 on using cocoon
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto: cziegeler@sundn.de
================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2]: Documentation System
Posted by Vadim Gritsenko <va...@verizon.net>.
Giacomo is right.
Vadim
> -----Original Message-----
> From: Giacomo Pati [mailto:giacomo@apache.org]
> Sent: Thursday, September 27, 2001 10:59 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [C2]: Documentation System
>
>
> Quoting Carsten Ziegeler <cz...@sundn.de>:
>
> > Hi Team,
> >
> > for the final release of C2 we should take some time and
> > update the documentation.
> > Several weeks ago, Berin made a very good proposal
> > for outlining the documentation
> > (see
> > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
> >
> > I think as we developed Cocoon we should also use
> > Cocoon to build the documentation!
> >
> > The Avalon project shows how to do this. Now, I
> > just started to adapt the Avalon documentation
> > build system to ours. Making it really working
> > well and maintainable will be a more complex
> > effort than I thought it is.
> > So before I go any further, we should
> > vote on this topic.
> >
> > So lets vote if we still should use stylebook
> > or we should "update" to Cocoon for docs
> > generation. Please note that this question
> > has nothing to do with the question of
> > the format the docs are written in!
> > That's a separate task!
> >
> > Although it's a lot of work my vote:
> > +1 on using cocoon
>
> I don't know if this voting is necessary. As Cocoon commiters our answer should
> be "yes we will"!
>
> Giacomo
>
> >
> >
> > Carsten
> >
> > Open Source Group sunShine - b:Integrated
> > ================================================================
> > Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > www.sundn.de mailto: cziegeler@sundn.de
> > ================================================================
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Documentation System
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Carsten Ziegeler <cz...@sundn.de>:
> Hi Team,
>
> for the final release of C2 we should take some time and
> update the documentation.
> Several weeks ago, Berin made a very good proposal
> for outlining the documentation
> (see
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
>
> I think as we developed Cocoon we should also use
> Cocoon to build the documentation!
>
> The Avalon project shows how to do this. Now, I
> just started to adapt the Avalon documentation
> build system to ours. Making it really working
> well and maintainable will be a more complex
> effort than I thought it is.
> So before I go any further, we should
> vote on this topic.
>
> So lets vote if we still should use stylebook
> or we should "update" to Cocoon for docs
> generation. Please note that this question
> has nothing to do with the question of
> the format the docs are written in!
> That's a separate task!
>
> Although it's a lot of work my vote:
> +1 on using cocoon
I don't know if this voting is necessary. As Cocoon commiters our answer should
be "yes we will"!
Giacomo
>
>
> Carsten
>
> Open Source Group sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.sundn.de mailto: cziegeler@sundn.de
> ================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Documentation System
Posted by Berin Loritsch <bl...@apache.org>.
Carsten Ziegeler wrote:
>
> Hi Team,
>
> for the final release of C2 we should take some time and
> update the documentation.
> Several weeks ago, Berin made a very good proposal
> for outlining the documentation
> (see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
>
> I think as we developed Cocoon we should also use
> Cocoon to build the documentation!
>
> The Avalon project shows how to do this. Now, I
> just started to adapt the Avalon documentation
> build system to ours. Making it really working
> well and maintainable will be a more complex
> effort than I thought it is.
> So before I go any further, we should
> vote on this topic.
>
> So lets vote if we still should use stylebook
> or we should "update" to Cocoon for docs
> generation. Please note that this question
> has nothing to do with the question of
> the format the docs are written in!
> That's a separate task!
>
> Although it's a lot of work my vote:
> +1 on using cocoon
+1 from Me!
Learning Cocoon is a difficult task in itself. You
will find that once the environment is set up, it is
easy to maintain. The problem is getting it set up.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2]: Documentation System
Posted by Carsten Ziegeler <cz...@sundn.de>.
> -----Ursprungliche Nachricht-----
> Von: Gianugo Rabellino [mailto:g.rabellino@bibop.it]
> Gesendet: Freitag, 28. September 2001 13:03
> An: cocoon-dev@xml.apache.org
> Betreff: Re: [C2]: Documentation System
>
>
> On Fri, Sep 28, 2001 at 10:49:13AM +0200, Carsten Ziegeler wrote:
> > > over yet actually). In the next ew weeks I will have
> > > some time to spare and I'm going to study in depth
> > > Cocoon and Avalo internals. Since I think that the
> > > best thing to do when studying code is to write notes
> > > that might well become documentation, I'm officially
> > > volunteering to write some of the needed docs: just
> > > let me know if you think I can be of any help and I
> > > will start right away.
> > >
> > Great!!! Just start - I think every area needs more docs.
>
> OK, thanks :) I'll try to follow as close as possible
> Berin's path. Just one question: Docbook, simplified Docbook,
> Apache DTD or what? I hate to redo my work ;)
>
Currently we use the Apache DTD; all xdocs are written using this,
so this should be the one to use.
But I think we will sooner or later switch to another one,
which will be properly docbook.
carsten
> Ciao,
>
> --
> Gianugo Rabellino
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Documentation System
Posted by Gianugo Rabellino <g....@bibop.it>.
On Fri, Sep 28, 2001 at 10:49:13AM +0200, Carsten Ziegeler wrote:
> > over yet actually). In the next ew weeks I will have
> > some time to spare and I'm going to study in depth
> > Cocoon and Avalo internals. Since I think that the
> > best thing to do when studying code is to write notes
> > that might well become documentation, I'm officially
> > volunteering to write some of the needed docs: just
> > let me know if you think I can be of any help and I
> > will start right away.
> >
> Great!!! Just start - I think every area needs more docs.
OK, thanks :) I'll try to follow as close as possible
Berin's path. Just one question: Docbook, simplified Docbook,
Apache DTD or what? I hate to redo my work ;)
Ciao,
--
Gianugo Rabellino
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2]: Documentation System
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Gianugo Rabellino wrote:
>
> On Thu, Sep 27, 2001 at 04:17:19PM +0200, Carsten Ziegeler wrote:
> > for the final release of C2 we should take some time and
> > update the documentation.
>
> The lack of good documentation can seriously impact
> Cocoon's wide acceptance, one of the biggest problems I
> had to face with C2 was exactly this one (I'm not
> over yet actually). In the next ew weeks I will have
> some time to spare and I'm going to study in depth
> Cocoon and Avalo internals. Since I think that the
> best thing to do when studying code is to write notes
> that might well become documentation, I'm officially
> volunteering to write some of the needed docs: just
> let me know if you think I can be of any help and I
> will start right away.
>
Great!!! Just start - I think every area needs more docs.
Carsten
> > I think as we developed Cocoon we should also use
> > Cocoon to build the documentation!
>
> So do I. :)
>
> Ciao,
>
> --
> Gianugo Rabellino
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Documentation System
Posted by Gianugo Rabellino <g....@bibop.it>.
On Thu, Sep 27, 2001 at 04:17:19PM +0200, Carsten Ziegeler wrote:
> for the final release of C2 we should take some time and
> update the documentation.
The lack of good documentation can seriously impact
Cocoon's wide acceptance, one of the biggest problems I
had to face with C2 was exactly this one (I'm not
over yet actually). In the next ew weeks I will have
some time to spare and I'm going to study in depth
Cocoon and Avalo internals. Since I think that the
best thing to do when studying code is to write notes
that might well become documentation, I'm officially
volunteering to write some of the needed docs: just
let me know if you think I can be of any help and I
will start right away.
> I think as we developed Cocoon we should also use
> Cocoon to build the documentation!
So do I. :)
Ciao,
--
Gianugo Rabellino
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2]: Documentation System
Posted by Stefano Mazzocchi <st...@apache.org>.
Carsten Ziegeler wrote:
>
> > Stefano Mazzocchi wrote
> >
> > Carsten Ziegeler wrote:
> > >
> > > Hi Team,
> > >
> > > for the final release of C2 we should take some time and
> > > update the documentation.
> > > Several weeks ago, Berin made a very good proposal
> > > for outlining the documentation
> > > (see
> > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
> > >
> > > I think as we developed Cocoon we should also use
> > > Cocoon to build the documentation!
> > >
> > > The Avalon project shows how to do this. Now, I
> > > just started to adapt the Avalon documentation
> > > build system to ours. Making it really working
> > > well and maintainable will be a more complex
> > > effort than I thought it is.
> > > So before I go any further, we should
> > > vote on this topic.
> > >
> > > So lets vote if we still should use stylebook
> > > or we should "update" to Cocoon for docs
> > > generation. Please note that this question
> > > has nothing to do with the question of
> > > the format the docs are written in!
> > > That's a separate task!
> > >
> > > Although it's a lot of work my vote:
> > > +1 on using cocoon
> >
> > Definately, this is exactly what I was going to do when I finish up the
> > image gallery stuff, but if you want to go start and lead the way, I'll
> > be even happier :)
> >
> Hmmm, when is your image gallery stuff finished? :-)
Touche' :)
> No seriously, the documentation is currently building well, but it's need
> some work for the images of the navigation bar. I hope I can
> finish a quick and little bit dirty version by monday.
I'm going to tackle the problem from a wider angle in order to provide
the best way to perform aggregation in order to come up with a good
book-like PDF and perform pagination on HTML (which is 98% done for the
image library and totally reusable on everything else).
This week I had some work to do (yes, people, now I have work to do as
well :) so didn't have time to dedicate to OSS, but this has now changed
(hopefully).
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2]: Documentation System
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Stefano Mazzocchi wrote
>
> Carsten Ziegeler wrote:
> >
> > Hi Team,
> >
> > for the final release of C2 we should take some time and
> > update the documentation.
> > Several weeks ago, Berin made a very good proposal
> > for outlining the documentation
> > (see
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
> >
> > I think as we developed Cocoon we should also use
> > Cocoon to build the documentation!
> >
> > The Avalon project shows how to do this. Now, I
> > just started to adapt the Avalon documentation
> > build system to ours. Making it really working
> > well and maintainable will be a more complex
> > effort than I thought it is.
> > So before I go any further, we should
> > vote on this topic.
> >
> > So lets vote if we still should use stylebook
> > or we should "update" to Cocoon for docs
> > generation. Please note that this question
> > has nothing to do with the question of
> > the format the docs are written in!
> > That's a separate task!
> >
> > Although it's a lot of work my vote:
> > +1 on using cocoon
>
> Definately, this is exactly what I was going to do when I finish up the
> image gallery stuff, but if you want to go start and lead the way, I'll
> be even happier :)
>
Hmmm, when is your image gallery stuff finished? :-)
No seriously, the documentation is currently building well, but it's need
some work for the images of the navigation bar. I hope I can
finish a quick and little bit dirty version by monday.
Carsten
> So +1 from me as well.
>
> --
> Stefano Mazzocchi One must still have chaos in oneself to be
> able to give birth to a dancing star.
> <st...@apache.org> Friedrich Nietzsche
> --------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Documentation System
Posted by Stefano Mazzocchi <st...@apache.org>.
Carsten Ziegeler wrote:
>
> Hi Team,
>
> for the final release of C2 we should take some time and
> update the documentation.
> Several weeks ago, Berin made a very good proposal
> for outlining the documentation
> (see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
>
> I think as we developed Cocoon we should also use
> Cocoon to build the documentation!
>
> The Avalon project shows how to do this. Now, I
> just started to adapt the Avalon documentation
> build system to ours. Making it really working
> well and maintainable will be a more complex
> effort than I thought it is.
> So before I go any further, we should
> vote on this topic.
>
> So lets vote if we still should use stylebook
> or we should "update" to Cocoon for docs
> generation. Please note that this question
> has nothing to do with the question of
> the format the docs are written in!
> That's a separate task!
>
> Although it's a lot of work my vote:
> +1 on using cocoon
Definately, this is exactly what I was going to do when I finish up the
image gallery stuff, but if you want to go start and lead the way, I'll
be even happier :)
So +1 from me as well.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: entity resolution for Documentation build - almost
Posted by Michael McKibben <mm...@ncube.com>.
I think there is some general confusion on how 'file' URLs should be
constructed. RFC 1738 describes the format explicitly as:
fileurl = "file://" [ host | "localhost" ] "/" fpath
So, "/usr/local/cocoon2" should be written as
file:///usr/local/cocoon2 (Unix)
file:///c:/usr/local/cocoon2 (Windows)
Notice the '///'. This is because the host part of the URL is null. I
could have written the URL as
file://localhost/usr/local/cocoon2 (Unix)
file://localhost/c:/usr/local/cocoon2 (Windows)
and this would have worked also. Interestingly, with JDK1.3
new File("/usr/local/cocoon2").toURL().toString() (Unix)
new File("c:/usr/local/cocoon2").toURL().toString() (Windows)
returns
'file:/usr/local/cocoon2' (Unix)
'file:/c:/usr/local/cocoon2' (Windows)
in apparent violation of the RFC! So now we have three equivalent ways to
specify a file URL in Java:
On Unix:
file:///usr/local/cocoon2
file://localhost/usr/local/cocoon2
file:/usr/local/cocoon2
On Windows:
file:///c:/usr/local/cocoon2
file://localhost/c:/usr/local/cocoon2
file:/c:/usr/local/cocoon2
Notice the file path must be absolute (which is why on Windows the drive
specification must be specified.)
Regards,
--mike
On Tue, 23 Oct 2001, David Crossley wrote:
> I have discovered the cause of my problem with getting
> "build docs" to work properly with the entity resolver.
> Remember that it fails for me (but is OK for others) with
> "Failed to create InputSource: file://usr/local/.......", and we
> supsect the // to be a problem. I also noticed a strange
> pathname for loading the catalog file with a "./" in the middle
> of it. So i supected a bad path for the "contextDir" argument.
>
> Sure enough, if i hard-code the full pathname into build.xml
> - <arg value="-c."/>
> + <arg value="-c/usr/local/cvs/xml-cocoon2/build/cocoon/documentation"/>
> then the "build docs" works properly, and i finally see the
> "catalog-test.html" with the ISOnum entity set being
> resolved using the catalog. Hooray ... but why?
>
> --David
>
> On Wed, 10 Oct 2001 Carsten wrote:
> > Hi David,
> >
> > sorry I can't reproduce this here. Running under Windows2k
> > everything is working fine and I always get file:/ urls.
> > So, if someone with linux can have a look at it?
> >
> > Carstem
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > Gesendet: Mittwoch, 10. Oktober 2001 10:11
> > > An: cocoon-dev@xml.apache.org
> > > Betreff: Re: entity resolution for Documentation build - almost
> > >
> > > Cartsen wrote:
> > > > Hi David,
> > > > I applied your patch to both cvs. Thanks!
> > > > I think the problem lies indeed in the double slashes
> > > > of your url (file://). Where is this url build?
> > >
> > > The URL is built in components/resolver/ResolverImpl.java
> > > in the resolveEntity() method. Note that everything is OK
> > > via normal servlet running - the URL starts with file:/
> > > However, when running "build docs" it gets file://
> > >
> > > You would be able to see it yourself, if you try to
> > > process the catalog-test.xml supplied with the last
> > > patch.
> > > cheers, David
> > >
> > > > Carsten
> > > >
> > > > > -----Ursprüngliche Nachricht-----
> > > > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > > > Gesendet: Montag, 8. Oktober 2001 14:17
> > > > > An: cocoon-dev@xml.apache.org
> > > > > Betreff: Re: entity resolution for Documentation build - almost
> > > > >
> > > > > I am frustratingly close to getting entity catalogs working for
> > > > > the documentation build, and need some help. Here are some
> > > > > patches so that you can try for yourself.
> > > > >
> > > > > The patch to build.xml adds to the prepare-docs target
> > > > > to copy the default catalog and its entities over to the
> > > > > documentation build space. That is all that is required to
> > > > > enable the entity resolver.
> > > > > The patch to documentation/cocoon.xconf adds the config
> > > > > parameters for catalog resolver.
> > > > >
> > > > > It is safe to apply those patches. Nothing is adversely affected.
> > > > > The DTDs and other entities are already being resolved to
> > > > > files relative to the XML instance document.
> > > > >
> > > > > However, if you declare a new entity set in an xdoc then
> > > > > you will strike trouble. The entity resolver does deliver the
> > > > > correct pathname for the entity set. However, we get ...
> > > > > -----
> > > > > Failed to create InputSource:
> > > > > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> > > > ces/entities/ISOnum.pen
> > > > -----
> > > > Is the failure because of the double-slash file:// ... ???
> > > > The actual pathname is correct.
> > > >
> > > > When running via the normal webapp under Tomcat the
> > > > InputSource is successful and the page is presented.
> > > > The only difference is single slash rather than double slash
> > > > after file:
> > > > file:/usr/local/...
> > > >
> > > > As a convenience to facilitate testing of entity resolution for
> > > > the documentation build, there is a new xdocs/catalog-test.xml
> > > > - you will need to add an entry your local book.xml
> > > >
> > > > cheers, David
> -------
> Platform is ...
> Linux RedHat 7.1
> Blackdown j2sdk-1.3.1
> -------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: entity resolution for Documentation build - almost
Posted by David Crossley <cr...@indexgeo.com.au>.
I have discovered the cause of my problem with getting
"build docs" to work properly with the entity resolver.
Remember that it fails for me (but is OK for others) with
"Failed to create InputSource: file://usr/local/.......", and we
supsect the // to be a problem. I also noticed a strange
pathname for loading the catalog file with a "./" in the middle
of it. So i supected a bad path for the "contextDir" argument.
Sure enough, if i hard-code the full pathname into build.xml
- <arg value="-c."/>
+ <arg value="-c/usr/local/cvs/xml-cocoon2/build/cocoon/documentation"/>
then the "build docs" works properly, and i finally see the
"catalog-test.html" with the ISOnum entity set being
resolved using the catalog. Hooray ... but why?
--David
On Wed, 10 Oct 2001 Carsten wrote:
> Hi David,
>
> sorry I can't reproduce this here. Running under Windows2k
> everything is working fine and I always get file:/ urls.
> So, if someone with linux can have a look at it?
>
> Carstem
>
> > -----Ursprüngliche Nachricht-----
> > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > Gesendet: Mittwoch, 10. Oktober 2001 10:11
> > An: cocoon-dev@xml.apache.org
> > Betreff: Re: entity resolution for Documentation build - almost
> >
> > Cartsen wrote:
> > > Hi David,
> > > I applied your patch to both cvs. Thanks!
> > > I think the problem lies indeed in the double slashes
> > > of your url (file://). Where is this url build?
> >
> > The URL is built in components/resolver/ResolverImpl.java
> > in the resolveEntity() method. Note that everything is OK
> > via normal servlet running - the URL starts with file:/
> > However, when running "build docs" it gets file://
> >
> > You would be able to see it yourself, if you try to
> > process the catalog-test.xml supplied with the last
> > patch.
> > cheers, David
> >
> > > Carsten
> > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > > Gesendet: Montag, 8. Oktober 2001 14:17
> > > > An: cocoon-dev@xml.apache.org
> > > > Betreff: Re: entity resolution for Documentation build - almost
> > > >
> > > > I am frustratingly close to getting entity catalogs working for
> > > > the documentation build, and need some help. Here are some
> > > > patches so that you can try for yourself.
> > > >
> > > > The patch to build.xml adds to the prepare-docs target
> > > > to copy the default catalog and its entities over to the
> > > > documentation build space. That is all that is required to
> > > > enable the entity resolver.
> > > > The patch to documentation/cocoon.xconf adds the config
> > > > parameters for catalog resolver.
> > > >
> > > > It is safe to apply those patches. Nothing is adversely affected.
> > > > The DTDs and other entities are already being resolved to
> > > > files relative to the XML instance document.
> > > >
> > > > However, if you declare a new entity set in an xdoc then
> > > > you will strike trouble. The entity resolver does deliver the
> > > > correct pathname for the entity set. However, we get ...
> > > > -----
> > > > Failed to create InputSource:
> > > > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> > > ces/entities/ISOnum.pen
> > > -----
> > > Is the failure because of the double-slash file:// ... ???
> > > The actual pathname is correct.
> > >
> > > When running via the normal webapp under Tomcat the
> > > InputSource is successful and the page is presented.
> > > The only difference is single slash rather than double slash
> > > after file:
> > > file:/usr/local/...
> > >
> > > As a convenience to facilitate testing of entity resolution for
> > > the documentation build, there is a new xdocs/catalog-test.xml
> > > - you will need to add an entry your local book.xml
> > >
> > > cheers, David
-------
Platform is ...
Linux RedHat 7.1
Blackdown j2sdk-1.3.1
-------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: entity resolution for Documentation build - almost
Posted by David Crossley <cr...@indexgeo.com.au>.
I have not heard any compliants that their "build docs"
crashed since we added xdocs/catalog-test.xml
So i presume that everyone's system works but mine.
Perhaps it is my JVM - i will go to get another.
--David
> Date: Thu, 11 Oct 2001 12:11:14 +0200
> From: "Carsten Ziegeler" <cz...@sundn.de>
>
> David,
>
> I added your test case to the CVS HEAD for making testing
> much easier for all of us.
>
> Yes, I did follow the process and retried it today again.
> Using Windows2K and SUN JDK 1.2.2 it works.
>
> Carsten
>
> > David Crossley wrote:
> >
> > Would someone on each platform please try the following
> > on a recent CVS HEAD ...
> > 1) edit documentation/cocoon.xconf to raise the catalog
> > verbosity level to 3
> > 2) add the attached "catalog-test.xml" to your xdocs/
> > ... note that the rest of the xdocs/*.xml do not yet challenge
> > the entity resolver. This doc declares an external entity
> > that cannot be found relative to xdocs/
> > 3) add a temporary entry to book.xml for catalog-test
> > 4) build docs
> > 5) tell us if you see the bug described below or
> > do you get a successful build.
> >
> > Carsten, did you follow that process to exercise the bug?
> >
> > thanks, David Crossley
> >
> > ------
> > Carsten Ziegeler said:
> > > Hi David,
> > > sorry I can't reproduce this here. Running under Windows2k
> > > everything is working fine and I always get file:/ urls.
> > > So, if someone with linux can have a look at it?
> > >
> > > Carstem
> > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > > Gesendet: Mittwoch, 10. Oktober 2001 10:11
> > > > An: cocoon-dev@xml.apache.org
> > > > Betreff: Re: entity resolution for Documentation build - almost
> > > >
> > > > Cartsen wrote:
> > > > > Hi David,
> > > > > I applied your patch to both cvs. Thanks!
> > > > > I think the problem lies indeed in the double slashes
> > > > > of your url (file://). Where is this url build?
> > > >
> > > > The URL is built in components/resolver/ResolverImpl.java
> > > > in the resolveEntity() method. Note that everything is OK
> > > > via normal servlet running - the URL starts with file:/
> > > > However, when running "build docs" it gets file://
> > > >
> > > > You would be able to see it yourself, if you try to
> > > > process the catalog-test.xml supplied with the last
> > > > patch.
> > > > cheers, David
> > > >
> > > > > Carsten
> > > > >
> > > > > > -----Ursprüngliche Nachricht-----
> > > > > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > > > > Gesendet: Montag, 8. Oktober 2001 14:17
> > > > > > An: cocoon-dev@xml.apache.org
> > > > > > Betreff: Re: entity resolution for Documentation build - almost
> > > > > >
> > > > > > I am frustratingly close to getting entity catalogs working for
> > > > > > the documentation build, and need some help. Here are some
> > > > > > patches so that you can try for yourself.
> > > > > >
> > > > > > The patch to build.xml adds to the prepare-docs target
> > > > > > to copy the default catalog and its entities over to the
> > > > > > documentation build space. That is all that is required to
> > > > > > enable the entity resolver.
> > > > > > The patch to documentation/cocoon.xconf adds the config
> > > > > > parameters for catalog resolver.
> > > > > >
> > > > > > It is safe to apply those patches. Nothing is adversely affected.
> > > > > > The DTDs and other entities are already being resolved to
> > > > > > files relative to the XML instance document.
> > > > > >
> > > > > > However, if you declare a new entity set in an xdoc then
> > > > > > you will strike trouble. The entity resolver does deliver the
> > > > > > correct pathname for the entity set. However, we get ...
> > > > > > -----
> > > > > > Failed to create InputSource:
> > > > > > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> > > > > ces/entities/ISOnum.pen
> > > > > -----
> > > > > Is the failure because of the double-slash file:// ... ???
> > > > > The actual pathname is correct.
> > > > >
> > > > > When running via the normal webapp under Tomcat the
> > > > > InputSource is successful and the page is presented.
> > > > > The only difference is single slash rather than double slash
> > > > > after file:
> > > > > file:/usr/local/...
> > > > >
> > > > > As a convenience to facilitate testing of entity resolution for
> > > > > the documentation build, there is a new xdocs/catalog-test.xml
> > > > > - you will need to add an entry your local book.xml
> > > > >
> > > > > cheers, David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: entity resolution for Documentation build - almost
Posted by Carsten Ziegeler <cz...@sundn.de>.
David,
I added your test case to the CVS HEAD for making testing
much easier for all of us.
Yes, I did follow the process and retried it today again.
Using Windows2K and SUN JDK 1.2.2 it works.
Carsten
> David Crossley wrote:
>
> Would someone on each platform please try the following
> on a recent CVS HEAD ...
> 1) edit documentation/cocoon.xconf to raise the catalog
> verbosity level to 3
> 2) add the attached "catalog-test.xml" to your xdocs/
> ... note that the rest of the xdocs/*.xml do not yet challenge
> the entity resolver. This doc declares an external entity
> that cannot be found relative to xdocs/
> 3) add a temporary entry to book.xml for catalog-test
> 4) build docs
> 5) tell us if you see the bug described below or
> do you get a successful build.
>
> Carsten, did you follow that process to exercise the bug?
>
> thanks, David Crossley
>
> ------
> Carsten Ziegeler said:
> > Hi David,
> > sorry I can't reproduce this here. Running under Windows2k
> > everything is working fine and I always get file:/ urls.
> > So, if someone with linux can have a look at it?
> >
> > Carstem
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > Gesendet: Mittwoch, 10. Oktober 2001 10:11
> > > An: cocoon-dev@xml.apache.org
> > > Betreff: Re: entity resolution for Documentation build - almost
> > >
> > > Cartsen wrote:
> > > > Hi David,
> > > > I applied your patch to both cvs. Thanks!
> > > > I think the problem lies indeed in the double slashes
> > > > of your url (file://). Where is this url build?
> > >
> > > The URL is built in components/resolver/ResolverImpl.java
> > > in the resolveEntity() method. Note that everything is OK
> > > via normal servlet running - the URL starts with file:/
> > > However, when running "build docs" it gets file://
> > >
> > > You would be able to see it yourself, if you try to
> > > process the catalog-test.xml supplied with the last
> > > patch.
> > > cheers, David
> > >
> > > > Carsten
> > > >
> > > > > -----Ursprüngliche Nachricht-----
> > > > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > > > Gesendet: Montag, 8. Oktober 2001 14:17
> > > > > An: cocoon-dev@xml.apache.org
> > > > > Betreff: Re: entity resolution for Documentation build - almost
> > > > >
> > > > > I am frustratingly close to getting entity catalogs working for
> > > > > the documentation build, and need some help. Here are some
> > > > > patches so that you can try for yourself.
> > > > >
> > > > > The patch to build.xml adds to the prepare-docs target
> > > > > to copy the default catalog and its entities over to the
> > > > > documentation build space. That is all that is required to
> > > > > enable the entity resolver.
> > > > > The patch to documentation/cocoon.xconf adds the config
> > > > > parameters for catalog resolver.
> > > > >
> > > > > It is safe to apply those patches. Nothing is adversely affected.
> > > > > The DTDs and other entities are already being resolved to
> > > > > files relative to the XML instance document.
> > > > >
> > > > > However, if you declare a new entity set in an xdoc then
> > > > > you will strike trouble. The entity resolver does deliver the
> > > > > correct pathname for the entity set. However, we get ...
> > > > > -----
> > > > > Failed to create InputSource:
> > > > > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> > > > ces/entities/ISOnum.pen
> > > > -----
> > > > Is the failure because of the double-slash file:// ... ???
> > > > The actual pathname is correct.
> > > >
> > > > When running via the normal webapp under Tomcat the
> > > > InputSource is successful and the page is presented.
> > > > The only difference is single slash rather than double slash
> > > > after file:
> > > > file:/usr/local/...
> > > >
> > > > As a convenience to facilitate testing of entity resolution for
> > > > the documentation build, there is a new xdocs/catalog-test.xml
> > > > - you will need to add an entry your local book.xml
> > > >
> > > > cheers, David
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: entity resolution for Documentation build - almost
Posted by David Crossley <cr...@indexgeo.com.au>.
Would someone on each platform please try the following
on a recent CVS HEAD ...
1) edit documentation/cocoon.xconf to raise the catalog
verbosity level to 3
2) add the attached "catalog-test.xml" to your xdocs/
... note that the rest of the xdocs/*.xml do not yet challenge
the entity resolver. This doc declares an external entity
that cannot be found relative to xdocs/
3) add a temporary entry to book.xml for catalog-test
4) build docs
5) tell us if you see the bug described below or
do you get a successful build.
Carsten, did you follow that process to exercise the bug?
thanks, David Crossley
------
Carsten Ziegeler said:
> Hi David,
> sorry I can't reproduce this here. Running under Windows2k
> everything is working fine and I always get file:/ urls.
> So, if someone with linux can have a look at it?
>
> Carstem
>
> > -----Ursprüngliche Nachricht-----
> > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > Gesendet: Mittwoch, 10. Oktober 2001 10:11
> > An: cocoon-dev@xml.apache.org
> > Betreff: Re: entity resolution for Documentation build - almost
> >
> > Cartsen wrote:
> > > Hi David,
> > > I applied your patch to both cvs. Thanks!
> > > I think the problem lies indeed in the double slashes
> > > of your url (file://). Where is this url build?
> >
> > The URL is built in components/resolver/ResolverImpl.java
> > in the resolveEntity() method. Note that everything is OK
> > via normal servlet running - the URL starts with file:/
> > However, when running "build docs" it gets file://
> >
> > You would be able to see it yourself, if you try to
> > process the catalog-test.xml supplied with the last
> > patch.
> > cheers, David
> >
> > > Carsten
> > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > > Gesendet: Montag, 8. Oktober 2001 14:17
> > > > An: cocoon-dev@xml.apache.org
> > > > Betreff: Re: entity resolution for Documentation build - almost
> > > >
> > > > I am frustratingly close to getting entity catalogs working for
> > > > the documentation build, and need some help. Here are some
> > > > patches so that you can try for yourself.
> > > >
> > > > The patch to build.xml adds to the prepare-docs target
> > > > to copy the default catalog and its entities over to the
> > > > documentation build space. That is all that is required to
> > > > enable the entity resolver.
> > > > The patch to documentation/cocoon.xconf adds the config
> > > > parameters for catalog resolver.
> > > >
> > > > It is safe to apply those patches. Nothing is adversely affected.
> > > > The DTDs and other entities are already being resolved to
> > > > files relative to the XML instance document.
> > > >
> > > > However, if you declare a new entity set in an xdoc then
> > > > you will strike trouble. The entity resolver does deliver the
> > > > correct pathname for the entity set. However, we get ...
> > > > -----
> > > > Failed to create InputSource:
> > > > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> > > ces/entities/ISOnum.pen
> > > -----
> > > Is the failure because of the double-slash file:// ... ???
> > > The actual pathname is correct.
> > >
> > > When running via the normal webapp under Tomcat the
> > > InputSource is successful and the page is presented.
> > > The only difference is single slash rather than double slash
> > > after file:
> > > file:/usr/local/...
> > >
> > > As a convenience to facilitate testing of entity resolution for
> > > the documentation build, there is a new xdocs/catalog-test.xml
> > > - you will need to add an entry your local book.xml
> > >
> > > cheers, David
AW: entity resolution for Documentation build - almost
Posted by Carsten Ziegeler <cz...@sundn.de>.
Hi David,
sorry I can't reproduce this here. Running under Windows2k
everything is working fine and I always get file:/ urls.
So, if someone with linux can have a look at it?
Carstem
> -----Ursprüngliche Nachricht-----
> Von: David Crossley [mailto:crossley@indexgeo.com.au]
> Gesendet: Mittwoch, 10. Oktober 2001 10:11
> An: cocoon-dev@xml.apache.org
> Betreff: Re: entity resolution for Documentation build - almost
>
>
> Cartsen wrote:
> > Hi David,
> > I applied your patch to both cvs. Thanks!
> > I think the problem lies indeed in the double slashes
> > of your url (file://). Where is this url build?
>
> The URL is built in components/resolver/ResolverImpl.java
> in the resolveEntity() method. Note that everything is OK
> via normal servlet running - the URL starts with file:/
> However, when running "build docs" it gets file://
>
> You would be able to see it yourself, if you try to
> process the catalog-test.xml supplied with the last
> patch.
> cheers, David
>
> > Carsten
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > > Gesendet: Montag, 8. Oktober 2001 14:17
> > > An: cocoon-dev@xml.apache.org
> > > Betreff: Re: entity resolution for Documentation build - almost
> > >
> > > I am frustratingly close to getting entity catalogs working for
> > > the documentation build, and need some help. Here are some
> > > patches so that you can try for yourself.
> > >
> > > The patch to build.xml adds to the prepare-docs target
> > > to copy the default catalog and its entities over to the
> > > documentation build space. That is all that is required to
> > > enable the entity resolver.
> > > The patch to documentation/cocoon.xconf adds the config
> > > parameters for catalog resolver.
> > >
> > > It is safe to apply those patches. Nothing is adversely affected.
> > > The DTDs and other entities are already being resolved to
> > > files relative to the XML instance document.
> > >
> > > However, if you declare a new entity set in an xdoc then
> > > you will strike trouble. The entity resolver does deliver the
> > > correct pathname for the entity set. However, we get ...
> > > -----
> > > Failed to create InputSource:
> > > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> > ces/entities/ISOnum.pen
> > -----
> > Is the failure because of the double-slash file:// ... ???
> > The actual pathname is correct.
> >
> > When running via the normal webapp under Tomcat the
> > InputSource is successful and the page is presented.
> > The only difference is single slash rather than double slash
> > after file:
> > file:/usr/local/...
> >
> > As a convenience to facilitate testing of entity resolution for
> > the documentation build, there is a new xdocs/catalog-test.xml
> > - you will need to add an entry your local book.xml
> >
> > cheers, David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: entity resolution for Documentation build - almost
Posted by David Crossley <cr...@indexgeo.com.au>.
Cartsen wrote:
> Hi David,
> I applied your patch to both cvs. Thanks!
> I think the problem lies indeed in the double slashes
> of your url (file://). Where is this url build?
The URL is built in components/resolver/ResolverImpl.java
in the resolveEntity() method. Note that everything is OK
via normal servlet running - the URL starts with file:/
However, when running "build docs" it gets file://
You would be able to see it yourself, if you try to
process the catalog-test.xml supplied with the last
patch.
cheers, David
> Carsten
>
> > -----Ursprüngliche Nachricht-----
> > Von: David Crossley [mailto:crossley@indexgeo.com.au]
> > Gesendet: Montag, 8. Oktober 2001 14:17
> > An: cocoon-dev@xml.apache.org
> > Betreff: Re: entity resolution for Documentation build - almost
> >
> > I am frustratingly close to getting entity catalogs working for
> > the documentation build, and need some help. Here are some
> > patches so that you can try for yourself.
> >
> > The patch to build.xml adds to the prepare-docs target
> > to copy the default catalog and its entities over to the
> > documentation build space. That is all that is required to
> > enable the entity resolver.
> > The patch to documentation/cocoon.xconf adds the config
> > parameters for catalog resolver.
> >
> > It is safe to apply those patches. Nothing is adversely affected.
> > The DTDs and other entities are already being resolved to
> > files relative to the XML instance document.
> >
> > However, if you declare a new entity set in an xdoc then
> > you will strike trouble. The entity resolver does deliver the
> > correct pathname for the entity set. However, we get ...
> > -----
> > Failed to create InputSource:
> > file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
> ces/entities/ISOnum.pen
> -----
> Is the failure because of the double-slash file:// ... ???
> The actual pathname is correct.
>
> When running via the normal webapp under Tomcat the
> InputSource is successful and the page is presented.
> The only difference is single slash rather than double slash
> after file:
> file:/usr/local/...
>
> As a convenience to facilitate testing of entity resolution for
> the documentation build, there is a new xdocs/catalog-test.xml
> - you will need to add an entry your local book.xml
>
> cheers, David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: entity resolution for Documentation build - almost
Posted by Carsten Ziegeler <cz...@sundn.de>.
Hi David,
I applied your patch to both cvs. Thanks!
I think the problem lies indeed in the double slashes
of your url (file://). Where is this url build?
Carsten
> -----Ursprüngliche Nachricht-----
> Von: David Crossley [mailto:crossley@indexgeo.com.au]
> Gesendet: Montag, 8. Oktober 2001 14:17
> An: cocoon-dev@xml.apache.org
> Betreff: Re: entity resolution for Documentation build - almost
>
>
> I am frustratingly close to getting entity catalogs working for
> the documentation build, and need some help. Here are some
> patches so that you can try for yourself.
>
> The patch to build.xml adds to the prepare-docs target
> to copy the default catalog and its entities over to the
> documentation build space. That is all that is required to
> enable the entity resolver.
> The patch to documentation/cocoon.xconf adds the config
> parameters for catalog resolver.
>
> It is safe to apply those patches. Nothing is adversely affected.
> The DTDs and other entities are already being resolved to
> files relative to the XML instance document.
>
> However, if you declare a new entity set in an xdoc then
> you will strike trouble. The entity resolver does deliver the
> correct pathname for the entity set. However, we get ...
> -----
> Failed to create InputSource:
> file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resour
ces/entities/ISOnum.pen
-----
Is the failure because of the double-slash file:// ... ???
The actual pathname is correct.
When running via the normal webapp under Tomcat the
InputSource is successful and the page is presented.
The only difference is single slash rather than double slash
after file:
file:/usr/local/...
As a convenience to facilitate testing of entity resolution for
the documentation build, there is a new xdocs/catalog-test.xml
- you will need to add an entry your local book.xml
cheers, David
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: entity resolution for Documentation build - almost
Posted by David Crossley <cr...@indexgeo.com.au>.
I am frustratingly close to getting entity catalogs working for
the documentation build, and need some help. Here are some
patches so that you can try for yourself.
The patch to build.xml adds to the prepare-docs target
to copy the default catalog and its entities over to the
documentation build space. That is all that is required to
enable the entity resolver.
The patch to documentation/cocoon.xconf adds the config
parameters for catalog resolver.
It is safe to apply those patches. Nothing is adversely affected.
The DTDs and other entities are already being resolved to
files relative to the XML instance document.
However, if you declare a new entity set in an xdoc then
you will strike trouble. The entity resolver does deliver the
correct pathname for the entity set. However, we get ...
-----
Failed to create InputSource:
file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation/resources/entities/ISOnum.pen
-----
Is the failure because of the double-slash file:// ... ???
The actual pathname is correct.
When running via the normal webapp under Tomcat the
InputSource is successful and the page is presented.
The only difference is single slash rather than double slash
after file:
file:/usr/local/...
As a convenience to facilitate testing of entity resolution for
the documentation build, there is a new xdocs/catalog-test.xml
- you will need to add an entry your local book.xml
cheers, David
entity resolution for Documentation build - almost
Posted by David Crossley <cr...@indexgeo.com.au>.
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
processing).
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:
file:/usr/local/cvs/xml-cocoon2/lib/xerces_1_4_3.jar
Resolved public: ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML
file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation//resources/entities/ISOnum.pen
Failed to create InputSource:
file://usr/local/cvs/xml-cocoon2/build/cocoon/documentation//resources/entities/ISOnum.pen
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2]: Documentation System
Posted by Carsten Ziegeler <cz...@sundn.de>.
I like to answer my own mails....
A first version of the documentation system is finished.
It generates all documents including the images for the
labels and headers.
The only thing currently missing is the "site" target,
which means for generating the documentation for the
web-site, a different book is used as there are some
other links available in the navigation bar.
Please, have a look at it and decide if we could switch.
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto: cziegeler@sundn.de
================================================================
> Carsten Ziegeler wrote:
> -----Ursprüngliche Nachricht-----
> Von: Carsten Ziegeler [mailto:cziegeler@sundn.de]
> Gesendet: Freitag, 28. September 2001 15:50
> An: cocoon-dev@xml.apache.org
> Betreff: AW: [C2]: Documentation System
>
>
> 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
>
> > Carsten Ziegeler wrote:
> >
> > Hi Team,
> >
> > for the final release of C2 we should take some time and
> > update the documentation.
> > Several weeks ago, Berin made a very good proposal
> > for outlining the documentation
> > (see
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
>
> I think as we developed Cocoon we should also use
> Cocoon to build the documentation!
>
> The Avalon project shows how to do this. Now, I
> just started to adapt the Avalon documentation
> build system to ours. Making it really working
> well and maintainable will be a more complex
> effort than I thought it is.
> So before I go any further, we should
> vote on this topic.
>
> So lets vote if we still should use stylebook
> or we should "update" to Cocoon for docs
> generation. Please note that this question
> has nothing to do with the question of
> the format the docs are written in!
> That's a separate task!
>
> Although it's a lot of work my vote:
> +1 on using cocoon
>
>
> Carsten
>
> Open Source Group sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.sundn.de mailto: cziegeler@sundn.de
> ================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2]: Documentation System
Posted by Carsten Ziegeler <cz...@sundn.de>.
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
> Carsten Ziegeler wrote:
>
> Hi Team,
>
> for the final release of C2 we should take some time and
> update the documentation.
> Several weeks ago, Berin made a very good proposal
> for outlining the documentation
> (see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99831665304443&w=2).
>
> I think as we developed Cocoon we should also use
> Cocoon to build the documentation!
>
> The Avalon project shows how to do this. Now, I
> just started to adapt the Avalon documentation
> build system to ours. Making it really working
> well and maintainable will be a more complex
> effort than I thought it is.
> So before I go any further, we should
> vote on this topic.
>
> So lets vote if we still should use stylebook
> or we should "update" to Cocoon for docs
> generation. Please note that this question
> has nothing to do with the question of
> the format the docs are written in!
> That's a separate task!
>
> Although it's a lot of work my vote:
> +1 on using cocoon
>
>
> Carsten
>
> Open Source Group sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.sundn.de mailto: cziegeler@sundn.de
> ================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org