forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs validation.xml
Date Sat, 16 Nov 2002 10:52:34 GMT
crossley    2002/11/16 02:52:34

  Modified:    src/documentation/content/xdocs validation.xml
  Log:
  Fixed some of the Warnings about not finding their project catalog.
  A workaround is available using ./build/tmp/context/WEB-INF/cocoon.xconf
  until we provide them with their own project cocoon.xconf file.
  
  Revision  Changes    Path
  1.10      +14 -15    xml-forrest/src/documentation/content/xdocs/validation.xml
  
  Index: validation.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/validation.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- validation.xml	16 Nov 2002 08:28:21 -0000	1.9
  +++ validation.xml	16 Nov 2002 10:52:34 -0000	1.10
  @@ -284,7 +284,7 @@
             types that Forrest provides.  Projects can augment this with their
             own catalog file in <code>${project.schema-dir}/catalog</code>.
             Add the "local-catalog" parameter to your
  -          <code>${project.content-dir}/WEB-INF/cocoon.xconf</code> as described
  +          <code>build/tmp/context/WEB-INF/cocoon.xconf</code> as described
             in that file. Remember to raise the "verbosity" level in
             <code>cocoon.xconf</code> if you suspect problems with your catalog.
           </p>
  @@ -299,21 +299,20 @@
             -- custom doctype --
             PUBLIC "-//Acme//DTD Download Documentation V1.0//EN" "dtd/download-v11.dtd"
           </source>
  -        <warning>Currently (2002-11-15) there are some large problems with the
  -          technique described here.  Firstly, if a custom DTD uses entities from
  -          Forrest, it must include those included files under
  -          ${project.schema-dir}/dtd, because currently Forrest's validation
  -          seems unable to look in catalog A for an entity used in a DTD found
  -          with catalog B.  In our case, A is a custom project's catalog snippet,
  -          and B is the Forrest catalog.  Secondly, Cocoon does not (without
  -          tweaking) deal with more than one catalog file, so if your project
  -          defines <code>${project.schema-dir}/catalog</code> then you will
  -          likely get errors about 'cannot resolve book-cocoon-v10.dtd'.  Until
  -          this is fixed (all help appreciated!) it is currently simpler just to
  +        <warning>Currently (2002-11-15) Forrest does not allow you to use a
  +          <code>cocoon.xconf</code> configuration file with your project.
  +          However, one is copied during the build to 
  +          <code>build/tmp/context/WEB-INF/cocoon.xconf</code> so after the
  +          first run of the '<code>forrest</code>' you can use that one.
  +          We are working on fixing this.
  +        </warning>
  +        <warning>Currently (2002-11-15) Forrest does not utilise your project
  +          OASIS catalog when doing '<code>forrest validate</code>'. This is
  +          because Ant does not read this additional catalog. Until this is
  +          fixed (all help appreciated!) it is currently simpler just to
             hand-validate custom XML files, use
             <code>project.validate.xdocs.excludes</code> to prevent validation
of
  -          new doc types and comment out the DOCTYPE declaration so Cocoon
  -          doesn't complain.
  +          new document types.
           </warning>
           <p>
             The format is described in <link href="&catalog_spec;">the
  
  
  

Mime
View raw message