crossley 02/02/02 18:09:30
Modified: src/webapp cocoon.xconf
Log:
- Clarify the description for <parser> component. It was somehow jumbled
during the previous change.
- Clarify notes about where to find descriptions of components and parameters.
Revision Changes Path
1.19 +13 -10 xml-cocoon2/src/webapp/cocoon.xconf
Index: cocoon.xconf
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/webapp/cocoon.xconf,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- cocoon.xconf 2 Feb 2002 04:35:16 -0000 1.18
+++ cocoon.xconf 3 Feb 2002 02:09:30 -0000 1.19
@@ -2,7 +2,12 @@
<cocoon version="2.0">
<!-- ================ Apache Cocoon configuration file ================== -->
-<!-- Please refer to the online documentation for full descriptions.
+<!-- For full description of the components and their parameters ...
+ - Apache Cocoon User Documentation at /userdocs/
+ - webapp/cocoon.xconf (this file) - describes each core component
+ - each optional component/.../*.xconf - these describe the parameters
+ for each component and are automatically included at build-time.
+
The notes that accompany the settings below are intended to be concise.
-->
@@ -15,9 +20,10 @@
If you have problems because your servlet environment uses its own
parser not conforming to JAXP 1.1 try using the alternative
XercesParser instead of the JaxpParser. To activate the XercesParser,
- move the line below starting with <parser ...> out of this comment block.
- You also than have to add a system property to your JVM
- (probably on the startup of your servlet engine like this:
+ change the class attribute to
+ class="org.apache.cocoon.components.parser.XercesParser"
+ You will also need to add a system property to your JVM,
+ probably on the startup of your servlet engine like this:
-Dorg.apache.cocoon.components.parser.Parser=org.apache.cocoon.components.parser.XercesParser
validate: This parameter causes the parser to be a validating parser.
@@ -25,14 +31,11 @@
(If you are going to use it elsewhere, then do so with caution.)
You really should have validated all of your XML documents already,
according to their proper DTD or schema. Do not expect Cocoon to do it.
-
- <parser class="org.apache.cocoon.components.parser.XercesParser"
+ <parameter name="validate" value="false"/>
+ -->
+ <parser class="org.apache.cocoon.components.parser.JaxpParser"
logger="core.parser">
- <parameter name="validate" value="false"/>
</parser>
- -->
- <parser logger="core.parser"/>
-
<!-- ============================ STORE ============================ -->
<!-- Store for the generated code. Used by compiled sitemap engine and
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
