crossley    02/05/16 22:03:09

  Modified:    src/documentation/xdocs/userdocs/concepts Tag:
                        cocoon_2_0_3_branch sitemap.xml
               src/documentation/xdocs/userdocs/generators Tag:
                        cocoon_2_0_3_branch file-generator.xml
  Log:
  Added explanation and clarification of file:// URLs.
  Submitted from: J.Pietschman
  Sync branch with HEAD.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.3.2.1   +29 -1     
xml-cocoon2/src/documentation/xdocs/userdocs/concepts/sitemap.xml
  
  Index: sitemap.xml
  ===================================================================
  RCS file: 
/home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/concepts/sitemap.xml,v
  retrieving revision 1.3
  retrieving revision 1.3.2.1
  diff -u -r1.3 -r1.3.2.1
  --- sitemap.xml       23 Feb 2002 16:47:39 -0000      1.3
  +++ sitemap.xml       17 May 2002 05:03:09 -0000      1.3.2.1
  @@ -620,7 +620,7 @@
         coming from a jar via http connection. 
        </li>
        <li>
  -      Use <code>file://foo/bar</code> to merge in xml content from the filesystem.
  +      Use <code>file:///foo/bar</code> to merge in xml content from the filesystem.
        </li>
        <li>
         Use <code>xmldb:&lt;your driver here&gt;://your.xmldb.host/db/foo/bar</code> 
to merge in xml content from a XML:DB compliant database.
  @@ -920,6 +920,34 @@
        </p>
       </s3>
      </s2>
  +  </s1>
  +
  +  <anchor id="file-url"/>
  +  <s1 title="File: URLs">
  +   <p>
  +    In your sitemaps you may need to refer to some resource that is outside
  +    the webapp context (e.g. UNIX /foo/bar/this.xsl
  +    e.g. Windows C:\foo\bar\this.xsl). You need to use the file: convention
  +    with the following syntax for absolute filesystem pathnames.
  +   </p>
  +
  +   <ul>
  +    <li>UNIX ... <code>file:///foo/bar/this.xsl</code></li>
  +    <li>Windows ... <code>file:///C:/foo/bar/this.xsl</code></li>
  +   </ul>
  +
  +   <p>
  +    Everything starting with a URI scheme identifer like &quot;file:&quot;
  +    or &quot;http:&quot; is an absolute URI. An absolute file URL is
  +    <code>file://some.host/some/path/to/file.ext</code>
  +    ... the host can be omitted, defaulting to localhost, so you can write
  +    <code>file:///some/path/to/file.ext</code>
  +   </p>
  +
  +   <p>
  +    Further information is at RFC2396:
  +    <link href="http://www.rfc-editor.org/rfc/rfc2396.txt";>Uniform Resource 
Identifiers (URI): Generic Syntax</link>
  +   </p>
     </s1>
   
     <s1 title="Protocols">
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.1   +4 -0      
xml-cocoon2/src/documentation/xdocs/userdocs/generators/file-generator.xml
  
  Index: file-generator.xml
  ===================================================================
  RCS file: 
/home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/generators/file-generator.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.2.1
  diff -u -r1.1 -r1.1.2.1
  --- file-generator.xml        3 Jan 2002 12:31:04 -0000       1.1
  +++ file-generator.xml        17 May 2002 05:03:09 -0000      1.1.2.1
  @@ -29,6 +29,10 @@
     <!-- The type attribute can be omitted as it is the default generator. -->
        ]]>
   </source>
  +   <p>
  +    You can use an absolute filesystem pathname. See explanation of
  +    <link href="../concepts/sitemap.html#file-url">file: URLs</link>
  +   </p>
                </s1>
        </body>
   </document>
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to