joerg 2004/03/10 03:37:27
Modified: . mount-table.xml.sample Log: *** keyword substitution change *** Revision Changes Path 1.3 +46 -46 cocoon-2.2/mount-table.xml.sample Index: mount-table.xml.sample =================================================================== RCS file: /home/cvs/cocoon-2.2/mount-table.xml.sample,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- mount-table.xml.sample 10 Mar 2004 08:43:23 -0000 1.2 +++ mount-table.xml.sample 10 Mar 2004 11:37:27 -0000 1.3 @@ -1,46 +1,46 @@ -<!-- - Copyright 1999-2004 The Apache Software Foundation - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. ---> -<mount-table> - <!-- - The mount table allows to mount directories external to the Cocoon webapp without - changing the main sitemap. To activate the mount-table, just copy or rename this file - to "mount-table.xml" to see it automatically activated. - - Each mount below will direct requests starting with the given uri-prefix to the corresponding - sitemap. The syntax is exactly the same as the one of <map:mount>. - - The mount-table is especially useful for two purposes: - - for all users, to mount into Cocoon external directories (demos, prototypes, projects) without - having to change the main Cocoon sitemap. This allows these mounts to "survive" a update to a - more recent version of Cocoon. - - - for cocoon contributors, to mount the source of Cocoon examples instead of their copy placed in - build/webapp by the build process. This avoids many of the hassles related to editing a copy of - the sources, often leading to sync problems. - --> - - <!-- - example: mount the woody source samples at "woody-samples/" - (don't forget the / at the end of the path name) - --> - <mount uri-prefix="woody-samples/" src="../../src/blocks/woody/samples/"/> - - - <!-- example: mount a prototype located elsewhere on the filesystem at "proto/" - (kept commented as the path is not likely to exist on your filesystem) --> - <mount uri-prefix="proto/" src="file://c:/my/projects/prototype/"/> - -</mount-table> +<!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<mount-table> + <!-- + The mount table allows to mount directories external to the Cocoon webapp without + changing the main sitemap. To activate the mount-table, just copy or rename this file + to "mount-table.xml" to see it automatically activated. + + Each mount below will direct requests starting with the given uri-prefix to the corresponding + sitemap. The syntax is exactly the same as the one of <map:mount>. + + The mount-table is especially useful for two purposes: + - for all users, to mount into Cocoon external directories (demos, prototypes, projects) without + having to change the main Cocoon sitemap. This allows these mounts to "survive" a update to a + more recent version of Cocoon. + + - for cocoon contributors, to mount the source of Cocoon examples instead of their copy placed in + build/webapp by the build process. This avoids many of the hassles related to editing a copy of + the sources, often leading to sync problems. + --> + + <!-- + example: mount the woody source samples at "woody-samples/" + (don't forget the / at the end of the path name) + --> + <mount uri-prefix="woody-samples/" src="../../src/blocks/woody/samples/"/> + + + <!-- example: mount a prototype located elsewhere on the filesystem at "proto/" + (kept commented as the path is not likely to exist on your filesystem) --> + <mount uri-prefix="proto/" src="file://c:/my/projects/prototype/"/> + +</mount-table>
