cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@cocoon.apache.org
Subject [Cocoon Wiki] Updated: BeginnerAdvancedWebappOrganisation
Date Fri, 23 Jul 2004 14:30:41 GMT
   Date: 2004-07-23T07:30:40
   Editor: ViPi <michbur@arcor.de>
   Wiki: Cocoon Wiki
   Page: BeginnerAdvancedWebappOrganisation
   URL: http://wiki.apache.org/cocoon/BeginnerAdvancedWebappOrganisation

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -36,15 +36,15 @@
   * Search for the line with <map:pipelines> . This is the start tag of the
    pipelines bracket near line 530.
   * Add following code snippet right AFTER the starttag <pipelines> and save 
-   your modifications:{{{
-     <map:pipeline>
-       <map:match pattern="work/**">
-         <map:mount check-reload="yes"
-                    reload-method="synchron"
-                    src="/work/sitemap.xmap"
-                    uri-prefix="work"/>
-      </map:match>
-     </map:pipeline>
+   your modifications:{{{
+     <map:pipeline>
+       <map:match pattern="work/**">
+         <map:mount check-reload="yes"
+                    reload-method="synchron"
+                    src="/work/sitemap.xmap"
+                    uri-prefix="work"/>
+      </map:match>
+     </map:pipeline>
 }}}
  *  Now the src for the mount is an absolute path. By this you can place your actual workfolder
at an arbitrary place within your filesystem. Create your work folder exactly at the location
you have specified in the src attribute and proceed as described in Part II above. In the
example snippet above i have choosen the location "/work" (see the src-attribute of the <map:mount>
tag) although the folder name is arbitrary.
 
@@ -58,21 +58,21 @@
 a generic sitemap similar to Part I above. I assume, you want to put some cocoon 
 applications into subfolders of /work, e.g. /work/coconuts and /work/cocobolts.
 Then you want to adress these applications separately with URL's like
-{{{
-http://localhost:8080/cocoon/work/coconuts
-http://localhost:8080/cocoon/work/cocobolts
+{{{
+http://localhost:8080/cocoon/work/coconuts
+http://localhost:8080/cocoon/work/cocobolts
 }}}
 Also this can be achieved with a slight modification of your pipeline.
 Go again to $cocoon_root/sitemap.xmap and modify your pipeline as follow:
-{{{
-<map:pipeline>
-  <map:match pattern="work/*/**">
-    <map:mount check-reload="yes"
-               reload-method="synchron"
-               src="/work/{1}/sitemap.xmap"
-               uri-prefix="work/{1}"/>
- </map:match>
-</map:pipeline>
+{{{
+<map:pipeline>
+  <map:match pattern="work/*/**">
+    <map:mount check-reload="yes"
+               reload-method="synchron"
+               src="/work/{1}/sitemap.xmap"
+               uri-prefix="work/{1}"/>
+ </map:match>
+</map:pipeline>
 }}}
 
 Note how this sitemap now resembles the very first code snippet for the
@@ -90,7 +90,7 @@
 
 to trigger cocoon to send an html index page back to the browser.
 This issue is worthwhile to create a separate page. Please look at
-BeginnerDefaultContext or [:Cocoon2.1.4EasyInstallation] for further reading.
+BeginnerDefaultContext or [:CocoonEasyInstallation] for further reading.
 
 ----
 ===  page metadata ===

Mime
View raw message