cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vgritse...@apache.org
Subject cvs commit: cocoon-2.0/src/webapp sitemap.xmap
Date Tue, 30 Mar 2004 20:08:39 GMT
vgritsenko    2004/03/30 12:08:39

  Modified:    src/webapp sitemap.xmap
  Log:
  Who let that "AFAIK" in?
  
  Revision  Changes    Path
  1.7       +4 -4      cocoon-2.0/src/webapp/sitemap.xmap
  
  Index: sitemap.xmap
  ===================================================================
  RCS file: /home/cvs/cocoon-2.0/src/webapp/sitemap.xmap,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- sitemap.xmap	29 Jul 2003 18:02:57 -0000	1.6
  +++ sitemap.xmap	30 Mar 2004 20:08:39 -0000	1.7
  @@ -531,7 +531,7 @@
   
     1) The top level elements are executed in order of appearance until
        one signals success. These top level elements are usually
  -     matchers. AFAIK other components are not supported for this.
  +     matchers.
   
        Other components are called depth-first to determine what
        fragments make up the processing pipeline. When a component
  @@ -543,9 +543,9 @@
        this, the pipeline may not be changed.
   
   
  -  You may have as many pipelines in your sitemap as you like. However,
  -  it seems that the only purposes would be to specify different error
  -  handlers.
  +  You may have as many pipelines in your sitemap as you like. Purposes
  +  for several pipelines would be to restrict access (internal-only
  +  attribute), and error handlers.
   -->
   
    <map:pipelines>
  
  
  

Mime
View raw message