cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ilgro...@apache.org
Subject svn commit: r1329674 [3/10] - in /cocoon/trunk/site/cocoon-core-site: ./ core/ core/2.2/ core/2.2/src/ core/2.2/src/site/ core/2.2/src/site/resources/ core/2.2/src/site/resources/images/ core/2.2/src/site/xdoc/ src/site/ src/site/resources/ src/site/re...
Date Tue, 24 Apr 2012 12:33:14 GMT
Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1261_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1261_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1261_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Block structure</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Block structure</h1><p>Technically, a block is a Java Archive (jar) file following a particular
+directory structure:</p><table class="bodyTable">
+<tbody>
+<tr class="a">
+<th>
+<p>Path</p>
+</th>
+<th>
+<p>Patterns</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+<tr class="b">
+<td><tt>/</tt><tt>COB-INF/sitemap.xmap</tt></td>
+<td><tt>-</tt></td>
+<td>
+<p>If the blocks uses  the SitemapServlet service, this is the default location
+of  the sitemap.</p>
+</td>
+</tr>
+<tr class="a">
+<td><tt>/COB-INF/config/spring/</tt></td>
+<td><tt>*.xml<br/>
+*.properties<br/>
+</tt></td>
+<td>
+<p>Configuration files for Spring beans, that are only available within this
+block. There is no way to access them from other blocks.</p>
+</td>
+</tr>
+<tr class="b">
+<td><tt>/COB-INF/config/properties/</tt></td>
+<td><tt>*.properties</tt></td>
+<td>
+<p>Properties available within the sitemap.</p>
+</td>
+</tr>
+<tr class="a">
+<td><tt>/COB-INF/</tt></td>
+<td>
+<p>*.*</p>
+</td>
+<td>
+<p>Cocoon resources</p>
+</td>
+</tr>
+<tr class="b">
+<td><tt>/META-INF/cocoon/spring/</tt></td>
+<td><tt>*.xml<br/>
+*.properties<br/>
+</tt></td>
+<td>
+<p>Configuration files for Spring beans, that are globally available. Make sure
+that the bean ids are unique.</p>
+</td>
+</tr>
+<tr class="a">
+<td><tt>/META-INF/cocoon/avalon/</tt></td>
+<td><tt>*.xconf<br/>
+*.xmap<br/>
+</tt></td>
+<td>
+<p>Avalon-style component configurations, that are globally available.</p>
+</td>
+</tr>
+<tr class="b">
+<td><tt>/META-INF/cocoon/properties/</tt></td>
+<td><tt>*.properties</tt></td>
+<td>
+<p>Default values for properties.</p>
+</td>
+</tr>
+<tr class="a">
+<td><tt>/META-INF/cocoon/properties/[running-mode]/</tt></td>
+<td><tt>*.properties</tt></td>
+<td>
+<p>Properties valid for particular running modes.</p>
+</td>
+</tr>
+<tr class="b">
+<td>
+<p>/</p>
+</td>
+<td>
+<p>*.*</p>
+</td>
+<td>
+<p>Java classes and resources</p>
+</td>
+</tr>
+</tbody>
+</table></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1263_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Overview</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Overview</h1><p>TODO:</p><ul>
+<li>use cases for blocks</li>
+<li>which problem do they solve</li>
+</ul></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1268_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Web application structure</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Web application structure</h1><h1>Content of a Cocon Web Application</h1><p>If you want to use Cocoon from within a web application, it expects following
+directory structure and files:</p><table class="bodyTable">
+<tbody>
+<tr class="a">
+<th>
+<p>Path</p>
+</th>
+<th>
+<p>Pattern</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+<tr class="b">
+<td><tt>WEB-INF/web.xml</tt></td>
+<td>
+<p>-</p>
+</td>
+<td>
+<p>Central configuration file for Java web applications. Find details below.</p>
+</td>
+</tr>
+<tr class="a">
+<td><tt>WEB-INF/cocoon/applicationContext.xml</tt></td>
+<td>
+<p>-</p>
+</td>
+<td>
+<p>Global spring context. Cocoon is initialized here. Find details below.</p>
+</td>
+</tr>
+<tr class="b">
+<td><tt>WEB-INF/cocoon/log4j.xconf</tt></td>
+<td>
+<p>-</p>
+</td>
+<td>
+<p>The logging configuration.</p>
+</td>
+</tr>
+<tr class="a">
+<td><tt>WEB-INF/cocoon/properties</tt></td>
+<td><tt>*.<tt>p</tt></tt><tt>roperties</tt></td>
+<td/>
+</tr>
+<tr class="b">
+<td><tt>WEB-INF/cocoon/properties/[running-mode]</tt></td>
+<td><tt>*.properties</tt></td>
+<td/>
+</tr>
+<tr class="a">
+<td>
+<p>*</p>
+</td>
+<td/>
+<td>
+<p>Cocoon web application (Note: Usually Cocoon applications are developed as
+blocks. This means that there is nothing in here.)</p>
+</td>
+</tr>
+</tbody>
+</table><h1>web.xml</h1><p>TBD</p><h1>applicationContext.xml</h1><p>TBD</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1269_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - XSLTTransformer</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">XSLTTransformer</h1><h1>Summary</h1><p>The XSLT stylesheet processor</p><h1>Basic information</h1><table class="bodyTable"><tbody><tr class="a"><th>Component type</th><td>Transformer</td></tr><tr class="b"><th>Cocoon block</th><td>core</td></tr><tr class="a"><th>Java class</th><td>org.apache.cocoon.transformation.XSLTTransformer</td></tr><tr class="b"><th>Name in Sitemap</th><td>xslt</td></tr><tr class="a"><th>Cacheable</th><td>Yes - Yes. Uses the last modification date of the xslt document for validation</td></tr></tbody></table><h1>Documentation</h1><p>No documentation available yet.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1331_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - FileGeneratorBean</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">FileGeneratorBean</h1><h1>Summary</h1><p>The <tt>FileGenerator</tt> is a class that reads XML from a source and
+generates SAX Events. The <tt>FileGenerator</tt> is cacheable.</p><h1>Basic information</h1><table class="bodyTable"><tbody><tr class="a"><th>Component type</th><td>Generator</td></tr><tr class="b"><th>Cocoon block</th><td>core</td></tr><tr class="a"><th>Java class</th><td>org.apache.cocoon.generation.FileGeneratorBean</td></tr><tr class="b"><th>Name in Sitemap</th><td>file</td></tr><tr class="a"><th>Cacheable</th><td>Yes - Uses the last modification date of the xml document for validation</td></tr></tbody></table><h1>Documentation</h1><p>No documentation available yet.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1336_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - PauseGeneratorBean</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">PauseGeneratorBean</h1><h1>Summary</h1><p>This generator extends the usual FileGenerator with a pause parameter. During
+generation of the content, this generator pauses for the given amount of time
+(in seconds).</p><h1>Basic information</h1><table class="bodyTable"><tbody><tr class="a"><th>Component type</th><td>Generator</td></tr><tr class="b"><th>Cocoon block</th><td>core</td></tr><tr class="a"><th>Java class</th><td>org.apache.cocoon.generation.PauseGeneratorBean</td></tr><tr class="b"><th>Name in Sitemap</th><td/></tr><tr class="a"><th>Cacheable</th><td>Yes</td></tr></tbody></table><h1>Documentation</h1><p>No documentation available yet.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1337_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - CSVGeneratorBean</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">CSVGeneratorBean</h1><h1>Summary</h1><p>A simple parser converting a Comma Separated Values (CSV) file into XML.</p><h1>Basic information</h1><table class="bodyTable"><tbody><tr class="a"><th>Component type</th><td>Generator</td></tr><tr class="b"><th>Cocoon block</th><td>core</td></tr><tr class="a"><th>Java class</th><td>org.apache.cocoon.generation.CSVGeneratorBean</td></tr><tr class="b"><th>Name in Sitemap</th><td/></tr><tr class="a"><th>Cacheable</th><td>Yes</td></tr></tbody></table><h1>Documentation</h1><p>No documentation available yet.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1339_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - StripNameSpacesTransformer</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">StripNameSpacesTransformer</h1><h1>Summary</h1><p>The <tt>StripNameSpacesTransformer</tt> is a class that can be plugged into a
+pipeline to strip all namespaces from a SAX stream. It is much faster (certainly
+for larger streams, but easily factor 100) then the conventional
+stripnamespaces.xsl</p><h1>Basic information</h1><table class="bodyTable"><tbody><tr class="a"><th>Component type</th><td>Transformer</td></tr><tr class="b"><th>Cocoon block</th><td>core</td></tr><tr class="a"><th>Java class</th><td>org.apache.cocoon.transformation.StripNameSpacesTransformer</td></tr><tr class="b"><th>Name in Sitemap</th><td>stripnamespaces</td></tr><tr class="a"><th>Cacheable</th><td>Yes - Yes</td></tr></tbody></table><h1>Documentation</h1><p>No documentation available yet.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1340_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    -->
+<document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
+  <properties>
+    <title>Cocoon Core - LinkRewriterReader</title>
+    <author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author>
+  </properties>
+  <body>
+    <div id="contentBody">
+      <div id="bodyText">
+        <h1 class="docTitle">LinkRewriterReader</h1>
+        <h1>Summary</h1>
+        <p>
+          <tt>LinkRewriterReader</tt> implements 
+          <tt>servlet:</tt> link rewriting in
+          text resources. It should be used especially for serving JavaScript files that
+          have paths refering to other blocks (
+          <tt>servlet:</tt> links).
+        </p>
+        <h1>Basic information</h1>
+        <table class="bodyTable">
+          <tbody>
+            <tr class="a">
+              <th>Component type</th>
+              <td>Reader</td>
+            </tr>
+            <tr class="b">
+              <th>Cocoon block</th>
+              <td>core</td>
+            </tr>
+            <tr class="a">
+              <th>Java class</th>
+              <td>org.apache.cocoon.servletservice.components.LinkRewriterReader</td>
+            </tr>
+            <tr class="b">
+              <th>Name in Sitemap</th>
+              <td/>
+            </tr>
+            <tr class="a">
+              <th>Cacheable</th>
+              <td>Yes - Yes</td>
+            </tr>
+          </tbody>
+        </table>
+        <h1>Documentation</h1>
+        <p>No documentation available yet.</p>
+      </div>
+    </div>
+  </body>
+</document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1344_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Introduction</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Introduction</h1><p>Cocoon has advanced control flow, the ability to describe the order of Web
+pages that have to be sent to the client, at any given point in time in an
+application.</p><p>Traditional Web applications try to model the control flow of a Web
+application by modeling the application as a finite state machine (FSM). In this
+model, the Web application is composed of multiple states, but the application
+can be only in one state at a time. Any request received by the application
+transitions it into a different state. During such a transition, the application
+may perform various side-effects, such as updating objects either in memory or
+in a database. Another important side-effect of such a transition is that a Web
+page is sent back to the client browser.</p><p>For simple Web applications, this model works fine. However, as the
+application grows, the number of states and transitions between them grows as
+well, and it becomes hard to visualize what's happening in the application.</p><p>Moreover, the interactions in some applications are more complex than a
+simple finite state machine. In such cases it's much easier to think of and
+implement the application as a program, rather than a FSM.</p><p>By using a high level programming concept called <em>continuations</em>,
+Cocoon tries to solve this problem, and promises to allow the control flow in
+Web applications to be modeled as a normal program.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1372_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Continuations</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Continuations</h1><h1>A different approach</h1><p>Web applications are essentially event-driven applications. Such applications
+have to react to events generated from the client browser, and they respond to
+these perhaps by changing their internal state and generating a response.</p><p>The result is that even a simple application that needs to collect some
+information from the user using more than one page, has to somehow maintain the
+input accumulated so far from the user. This input is a characteristic of the
+application state. Another characteristic of the application state is where the
+program processing is.</p><p>Let's look at an example. Suppose we want to write a very simple calculator,
+which collects the numbers to be added, as well as the operator, each in a
+separate page. It would be very nice if we could write something like this:</p><pre>function calculator()
+{
+  var a, b, operator;
+
+  cocoon.sendPageAndWait("getA.html");
+  a = cocoon.request.get("a");
+
+  cocoon.sendPageAndWait("getB.html");
+  b = cocoon.request.get("b");
+
+  cocoon.sendPageAndWait("getOperator.html");
+  operator = cocoon.request.get("op");
+
+  try {
+    if (operator == "plus")
+      cocoon.sendPage("result.html", {result: a + b});
+    else if (operator == "minus")
+      cocoon.sendPage("result.html", {result: a - b});
+    else if (operator == "multiply")
+      cocoon.sendPage("result.html", {result: a * b});
+    else if (operator == "divide")
+      cocoon.sendPage("result.html", {result: a / b});
+    else
+      cocoon.sendPage("invalidOperator.html", {operator: operator});
+  }
+  catch (exception) {
+    cocoon.sendPage("error.html", {message: "Operation failed: " + exception.toString()});
+  }
+}
+</pre><p>In this example, the <tt>calculator</tt> function is called to start the
+calculator application. We'd like the <tt>sendPageAndWait</tt> function to be a
+special function, that takes as arguments an HTML file to be sent as response,
+and some optional data that needs to be placed dynamically in it. We would like
+<tt>sendPageAndWait</tt> to send the response page and then block the executing
+thread, until the user clicks on a link in the response page, which sends a
+request back to the server. This request resumes the processing at the point it
+was left, right after the call to <tt>sendPageAndWait</tt>.</p><p>This approach looks very powerful, since the flow of pages within the
+application can be described as a normal program. Using this approach you no
+longer have to think of your Web application as a finite state machine, which
+transitions from one state to another, and in the process generates response
+pages.</p><p>A big disadvantage of the approach above is that we need to maintain a thread
+alive until the user hits the link on the response page. This is clearly very
+expensive!</p><p>It would be very nice if we could capture the state of the application, its
+stack of function calls, which includes local variables, the global variables
+and the program counter, and save them into an object. If this object would give
+us the ability to restart the processing from the point stored in it, this would
+be what we need!</p><h1>What are continuations?</h1><p>A continuation is exactly the type of object that we need. Think of a
+continuation as an object that, for a given point in your program, contains a
+snapshot of the stack trace, including all the local variables, and the program
+counter. You can not only store these things in the continuation object, but
+also restore the execution of the program from a continuation object. This means
+that the stack trace and the program counter of the running program become the
+ones stored in a continuation.</p><p>Continuations are powerful concepts from the world of functional languages,
+like <a href="http://www.schemers.org/">Scheme</a>, but they are becoming
+popular in other languages as well.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1373_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,214 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Views</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Views</h1><p>Apache Cocoon provides "views" to a resource. Defining a pipeline in a
+sitemap specifies the different stages of processing a resource. A view defines
+an exit point in the pipeline processing.</p><p>Views are yet another sitemap component. Unlike the rest, they are not
+inherited by sub-sitemaps and they are orthogonal to the resource and pipeline
+definitions. In the following we will not distinguish between resources and
+pipelines because their differences are not relevant here. So, when we talk
+about pipelines the said is valid for resources as well.</p><p>Basically, views let you specify exit points of your pipelines that are taken
+whenever a particular view is requested. The processing continues with the
+definitions in the requested view. The advantage over selectors that could
+achieve the same is, that these exit points are not necessarily declared for
+each pipeline individually, but once per sitemap.</p><h1>Motivation</h1><p>Implementing a semantic search feature is the main motivation to offer views
+in Apache Cocoon.</p><p>A sitemap defines the URI space of a Cocoon application. Apache Cocoon offers
+a fairly sophisticated URI space mapping mechanism. Defining pipelines in a
+sitemap you define this mapping. It's generally a mistake to map a file system
+(or a directory server, or a database repository) one-to-one with the URI space,
+since it leads to easily broken links and potential security issues.</p><p>Browsers requests resources of this URI space. The response of a browser
+request is normally intended for presenting to a human being. It may be
+augmented with navigation controls, and advertisements. An indexer of a search
+engines requests resources of this URI space, too. In contrast to a browser an
+indexer is interested in the bare content of a resource.</p><p>Views can access the original content of a resource. For example, you can now
+index a document resource, requesting the "content" view of the resource lacking
+the aggregation with navigation controls, and advertisements. You can now index
+the text inside a logo, if you are given the SVG content that generated the
+raster image. You can index the PDF content without having to implement a PDF
+parser since you request the "content" view of the resource obtaining an easily
+parsable XML file.</p><h1>Defining A View</h1><p>You declare a view in the sitemap. The definition of a view may define
+further processing steps. You are not allowed to define a generator step for a
+view, as the content of a view is the xml content from a view's exit point. The
+most simple view just serializes the xml content to xml.</p><p>A view element is identified by its name, and its label. You specify the name
+of a view by the attribute name, and its label either by the attribute
+from-label, or by the attribute from-position. The following list explains the
+attributes in more detail.</p><ul>
+<li>The attribute name specifies the name of view. Each view must have a unique
+name. If you request a view you have to specify the view name.</li>
+<li>The attribute from-label defines a label name of a pipeline exit point. You
+can choose any name you like, as a label name, except "first", and "last".</li>
+<li>The attribute from-position may have only following values "first", and
+"last". The special label "first" is the pipeline exit point after the generator
+processing stage. The special label "last" is the pipeline exit point right
+before the serializer processing stage. The labels "first", and "last" are set
+by the sitemanager automatically.</li>
+</ul>The following example is a simple resource view, just serializing the xml
+content of the view's exit point.<pre>&lt;map:views&gt;
+ &lt;map:view name="content" from-label="content"&gt;
+   &lt;map:serialize type="xml"/&gt;
+  &lt;/map:view&gt;
+&lt;/map:views&gt;
+</pre>The next example performs an xslt transformation before serializing to xml.
+<pre>&lt;map:views&gt;
+ &lt;map:view name="dublin-core" from-label="dublin-core"&gt;
+   &lt;map:transform src="stylesheets/document2dublin-core.xsl"/&gt;
+   &lt;map:serialize type="xml"/&gt;
+  &lt;/map:view&gt;
+&lt;/map:views&gt;
+</pre>The last example defines a view specifying the position-from attribute
+"last", and serializing to pdf, for a pdf-aware only indexer, or archiver.<pre>&lt;map:views&gt;
+ &lt;map:view name="full-document-content" from-position="last"&gt;
+   &lt;map:transform src="stylesheets/document2fo.xsl"/&gt;
+   &lt;map:serialize type="fo2pdf"/&gt;
+  &lt;/map:view&gt;
+&lt;/map:views&gt;
+</pre><h1>Placing Labels</h1><p>You place labels to define a pipeline exit point. A pipeline exit point may
+be shared by more than a single view.</p><p>Defining a pipeline exit point you have to add an attribute "label" to a
+sitemap element. The following sitemap elements are label aware:</p><table class="bodyTable">
+<tbody>
+<tr class="a">
+<th>
+<p>Sitemap Element</p>
+</th>
+<th>
+<p>Description</p>
+</th>
+</tr>
+<tr class="b">
+<td>
+<p>map:generator</p>
+</td>
+<td>
+<p>A generator element is allowed to have a label, eg. <tt>&lt;map:generator
+name="foo" src="bar" label="content"/&gt;</tt>. The xml content produced by the
+generator is passed to the requested view. Moreover requesting a "first" view
+has the same effect as labelling the first generator of pipeline.</p>
+</td>
+</tr>
+<tr class="a">
+<td>
+<p>map:generate</p>
+</td>
+<td>
+<p>A generate element is allowed to have a label attribute, eg.
+<tt>&lt;map:generate type="foo" label="content"/&gt;</tt>. The xml content
+produced by the generator is passed to the requested view. Moreover requesting a
+"first" view has the same effect as labelling the first generator of pipeline.
+</p>
+</td>
+</tr>
+<tr class="b">
+<td>
+<p>map:transformer</p>
+</td>
+<td>
+<p>A transformer element is allowed to have a label attribute, eg.
+<tt>&lt;map:transformer name="foo" src="bar"
+label="augmented-content"/&gt;</tt>. The xml content produced by the transformer
+is passed to the requested view.</p>
+</td>
+</tr>
+<tr class="a">
+<td>
+<p>map:transform</p>
+</td>
+<td>
+<p>A transform element is allowed to have a label attribute, eg.
+<tt>&lt;map:transform type="foo" label="augmented-content"/&gt;</tt>. The xml
+content produced by the transformer is passed to the requested view.</p>
+</td>
+</tr>
+<tr class="b">
+<td>
+<p>map:aggregate</p>
+</td>
+<td>
+<p>An aggregte element is allowed to have a label attribute, eg.
+<tt>&lt;map:aggregate element="foo" label="all-news"/&gt;</tt>. The xml content
+produced by the aggregate is passed to the requested view.</p>
+</td>
+</tr>
+<tr class="a">
+<td>
+<p>map:part</p>
+</td>
+<td>
+<p>A part element of an aggregate element is allowed to have a label attribute.
+eg. <tt>&lt;map:part src="foo" label="news-only"/&gt;</tt>. The xml content
+produced by the part only is passed to the requested view.</p>
+</td>
+</tr>
+</tbody>
+</table><p>A label attribute may hold 1 or more label names, separated by comma or
+blank, eg. <tt>&lt;map:generate src="foo" label="label1, label2"/&gt;</tt>.</p><h1>Placing Labels Summary</h1><p>As described above you have a wide range of choice for placing labels. You
+may even place labels to part elements, and to pipelines being the source of a
+labelled part element. The following paragraphs summarize some of the hot
+features.</p><p>You can use more that one label-value (label="content,link rdf") separated by
+comma or blank.</p><p>The aggregate element can have a label attribute which acts as on a
+generator, or transformer (all part elements are collected).</p><p>Part elements can have a label attribute. In this case only those parts are
+collected which corresponds to the requested view.</p><p>If you refer to sources via the cocoon:/ protocol the requested view will be
+propagated.</p><div class="note"><div><strong>Note: </strong>The element label is deprecated, and being not supported
+anymore. Thus you have to rewrite your sitemap if you are using
+<tt>&lt;map:label name="foobar"/&gt;</tt>.</div></div><p>Rewrite your sitemap if you were using label elements, moving the label name
+up to the previous xml producer. For example rewrite your sitemap:</p><pre>...
+&lt;map:generate src="foo"/&gt;
+&lt;map:transform type="bar"/&gt;
+&lt;map:label name="mylabel"/&gt;
+&lt;map:serialize/&gt;
+...</pre><p>...to this sitemap:</p><pre>...
+&lt;map:generate src="foo"/&gt;
+&lt;map:transform type="bar" label="mylabel"/&gt;
+&lt;map:serialize/&gt;
+...</pre><h1>View Processing</h1><p>The samples sitemap contains two view definitions. One of them looks like the
+excerpt below.</p><pre>&lt;map:views&gt;
+ &lt;map:view name="content" from-label="content"&gt;
+   &lt;map:serialize type="xml"/&gt;
+  &lt;/map:view&gt;
+&lt;/map:views&gt;
+</pre><p>It only defines what processing steps should be taken, after some exit point
+labelled "content" is reached. In all this case just a serializer is used to
+further process the document.</p><h1>Exit Points</h1><p>A look at the pipelines reveals no label "content". But a closer look at the
+defined components show this:</p><pre>&lt;map:components&gt;
+ &lt;map:generators default="file"&gt;
+  &lt;map:generator name="file"        
+                 src="org.apache.cocoon.generation.FileGenerator"
+                 label="content"/&gt;
+  &lt;map:generator name="directory"   
+                 src="org.apache.cocoon.generation.DirectoryGenerator"
+                 label="content"/&gt;
+  &lt;map:generator name="serverpages" 
+                 src="org.apache.cocoon.generation.ServerPagesGenerator"
+                 label="content"/&gt;
+  ...</pre><p>Here a number of generators are declared, each one has a label attribute.
+Now, everytime one of these generators is used in a pipeline, an exit point
+"content" is generated, just after the generator has been executed.</p><p>This is not limited to generators - every sitemap component can be augmented
+with a view label.</p><p>Two special labels exist: "first" and "last". These are automatically
+declared for every pipeline, after the first component and after the last
+respectively. This is used by the second view in the samples sitemap.</p><pre>&lt;map:view name="links" from-position="last"&gt;
+ &lt;map:serialize type="links"/&gt;
+&lt;/map:view&gt;</pre><h1>Requesting A View</h1><p>The current way for Cocoon to access views is fixed as a special URI query
+parameter <tt>cocoon-view</tt>.</p><p>For example querying the view <tt>content</tt> of the page:</p><pre>http://localhost:8080/cocoon/documents/index.html</pre><p>You use following URL:</p><pre>http://localhost:8080/cocoon/documents/index.html?cocoon-view=content</pre><p>Suggestions for further accessing views are:</p><ul>
+<li>React on a "variant" HTTP header (nothing cocoon specific since the concept
+could be impelemented later on by other publishing frameworks).</li>
+<li>React on URI extension: for example <tt>http://host/path/file.view</tt>,
+that is something that can be done by configuring the sitemaps manually. (where
+<tt>http://host/path/index</tt> is the default resource, and
+<tt>index.content</tt> is the XML view of the content).</li>
+</ul><div class="note"><div><strong>Note: </strong>Since views are orthogonal to pipelines, keep in mind to remove
+any unwanted view from a deployed application.</div></div></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1374_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,159 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Actions</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Actions</h1><h1>What is an Action?</h1><p>Apache Cocoon has a rich set of tools for publishing web documents, and while
+XSP and Generators provide alot of functionality, they still mix content and
+logic to a certain degree. The Action was created to fill that gap. Because the
+Cocoon Sitemap provides a mechanism to select the pipeline at run time, we
+surmised that sometimes we need to adjust the pipeline based on runtime
+parameters or even the contents of the Request parameter. Without the use of
+Actions this would make the sitemap almost incomprehensible.</p><p>The quick and dirty definition of an Action is "a Sitemap Component that
+manipulates runtime parameters". Actions must be ThreadSafe and they can be as
+complex as you need. The Action is the proper place to handle form processing
+and even dynamic navigation. The Action is differentiated from the other sitemap
+components (Generator, Transformer, Serializer and Reader) primarily by the fact
+that it does not produce any display data. <a href="NO_LINK">actions.txt</a>
+contains excerpts from discussions on the cocoon-dev mailing list regarding
+Actions.</p><h1>When to use an Action instead of Control Flow (e.g. Flowscript)</h1><p>TBD</p><h1>Actions at Work</h1><p>Actions are components that allow two way communication between the Sitemap
+and the Action. This section describes how to define them in the sitemap and
+create one in real life. We are going to write an Action that is our version of
+"Hello World".</p><p>The problem domain is this: we "need" a component that will create an HTTP
+request parameter named "hello" with a value of "world" and it will create a
+sitemap parameter named "world" with a value of "hello". Why? So we can show you
+the two manners in which the Action can be used and let your imagination go from
+there.</p><section name="Creating the Action" style="background:none;padding:0;"/><p>There is nothing like a little sample code to get your feet wet. We are
+performing something very simple here, but you can get more complex examples
+from the Cocoon code-base.</p><pre>package test;
+
+import org.apache.avalon.framework.parameters.Parameters;
+import org.apache.cocoon.acting.AbstractAction;
+import java.util.Map;
+import java.util.HashMap;
+import org.apache.cocoon.environment.ObjectModelHelper;
+import org.apache.cocoon.environment.Redirector;
+import org.apache.cocoon.environment.Request;
+import org.apache.cocoon.environment.SourceResolver;
+import org.xml.sax.EntityResolver;
+
+public class HelloWorldAction extends AbstractAction {
+  public Map act (Redirector redirector, 
+                  SourceResolver resolver, 
+                  Map objectModel, 
+                  String source, 
+                  Parameters params) {
+    Map sitemapParams = new HashMap();
+    sitemapParams.put("world", "hello");
+
+    Request request = ObjectModelHelper.getRequest(objectModel);
+
+    request.setAttribute("hello", "world");
+
+    return sitemapParams;
+  }
+}
+</pre><section name="Using the Action" style="background:none;padding:0;"/><p>In order to use the Action we just created, we need to define it in the
+sitemap. After it has been defined, we must use it in the sitemap.</p><h3>Defining the Action</h3><pre>&lt;map:actions&gt;
+  &lt;map:action name="hello-world" src="test.HelloWorldAction"/&gt;
+&lt;/map:actions&gt;
+</pre><h3>Using the Action</h3><pre>&lt;map:match pattern="file"&gt;
+  &lt;map:act type="hello-world"&gt;
+    &lt;map:generate type="serverpages" src="{world}_world.xsp"/&gt;
+  &lt;/map:act&gt;
+  &lt;map:serialize/&gt;
+&lt;/map:match&gt;
+</pre><p>Using this approach, we will generate the file named <tt>hello_world.xsp</tt>
+because the value of the Sitemap parameter <tt>{world}</tt> is <tt>hello</tt>.
+Also, the file <tt>hello_world.xsp</tt> can use the request attribute
+<tt>hello</tt> to produce the value <tt>world</tt>.</p><pre>&lt;para&gt;Hello &lt;xsp-request:get-attribute name="hello"/&gt;.&lt;/para&gt;
+</pre><section name="Communication between Sitemap and Action" style="background:none;padding:0;"/><p>As stated previously there is a two way communication between the Sitemap and
+the Action. The Sitemap can pass the parameters and the source attribute to the
+Action and the Action can return a Map object with new values which can be used
+in the sitemap.</p><pre>&lt;map:match pattern="file"&gt;
+  &lt;map:act type="hello-world" src="optional src"&gt;
+    &lt;!-- and here come the parameters: --&gt;
+    &lt;map:parameter name="first parameter" value="test"/&gt;
+
+    &lt;map:generate type="serverpages" src="{world}_world.xsp"/&gt;
+  &lt;/map:act&gt;
+  &lt;map:serialize/&gt;
+&lt;/map:match&gt;
+</pre><p>This Map object does not replace the previous Map object, but is stacked on
+top of it. The other Map objects are still accessible through a path expression.
+</p><pre>&lt;map:match pattern="*"&gt;
+  &lt;map:act type="validate-session"&gt;
+    &lt;map:generate type="serverpages" src="{../1}.xsp"/&gt;
+  &lt;/map:act&gt;
+  &lt;map:serialize/&gt;
+&lt;/map:match&gt;
+</pre><p>The above example shows how to access the next to last map by prefixing the
+key with <tt>../</tt>.</p><section name="Flow Control" style="background:none;padding:0;"/><p>In addition to delivering values to the Sitemap, the Action can also control
+the flow. If the action returns <tt>null</tt> all statements inside the
+<tt>map:act</tt> element are not executed. So, if in the example above the hello
+world action would return <tt>null</tt> the server page generator would not be
+activated.</p><p>In other words: The statements within the <tt>map:act</tt> element are
+<em>only</em> executed if the action returns at least an empty Map object.</p><h1>Action Sets</h1><p>You can arrange actions in an action set. The sitemap calls the act method of
+those actions in the sequence they are defined in the action set. It is possible
+to signal to the sitemap to call an action only if the Environment's
+<tt>getAction</tt> method returns a String identical to the value supplied with
+an action attribute. In the current implementation of the HttpEnvironment the
+value returned by the getAction method is determined by a http request
+parameter. The Environment looks for a request parameter with a prefix
+"cocoon-action-" followed by an action name.</p><pre>&lt;input type="submit" name="cocoon-action-ACTIONNAME" value="click here to do something"&gt;
+</pre><div class="note"><div><strong>Note: </strong>The orginal "cocoon-action" syntax is deprecated but still
+supported!</div></div><p>Above we have seen that a successfully executed action returns a Map object
+that can be used to communicate with the sitemap. In case of an action set this
+is similar. With action sets all returned Map objects are merged into a single
+Map. Of course a Map can contain only one value per key so that if multiple
+actions within an action set use the same key to communicate to the sitemap,
+only the last one "survives".</p><p>So far let's have a look at at possible action set definition:</p><pre>&lt;map:action-sets&gt;
+  &lt;map:action-set name="shop-actions"&gt;
+    &lt;map:act type="session-invalidator" action="logoff"/&gt;
+    &lt;map:act type="session-validator"/&gt;
+    &lt;map:act type="cart-add" action="addItem"/&gt;
+    &lt;map:act type="cart-remove" action="removeItem"/&gt;
+    &lt;map:act type="cart-remove-all" action="removeAll"/&gt;
+    &lt;map:act type="cart-update" action="updateQty"/&gt;
+    &lt;map:act type="order-add" action="addOrder"/&gt;
+    &lt;map:act type="order-verify" action="verifyOrder"/&gt;
+    &lt;map:act type="screen-navigator" src="{1}"/&gt;
+  &lt;/map:action-set&gt;
+&lt;/map:action-sets&gt;
+</pre><p>And this is a possible pipeline snipped which uses this action set:</p><pre>   &lt;map:match pattern="*"&gt;
+    &lt;map:act set="shop-actions"&gt;     &lt;--- HERE --&gt;
+     &lt;map:generate  type="serverpages" src="docs/xsp/{nextpage}.xsp"/&gt;
+     &lt;map:transform src="stylesheets/page2html.xsl"/&gt;
+     &lt;map:serialize type="html"/&gt;
+    &lt;/map:act&gt;
+   &lt;/map:match&gt;
+</pre><p>Let me explain some of those actions in the set first.</p><p>The "session-invalidator" action gets called when an action of logoff is
+requested (ie. a html submit button named "cocoon-action-logoff" was pressed).
+</p><p>The "session-validator" action is called on every request. It assures that an
+http session is created and available to the other sitemap components (other
+actions and xsp pages selected for resource production).</p><p>The other actions in the set with an action attribute do specific things like
+adding an item to the cart, removing one or all items from the cart, etc. They
+are called depending on the value returned by the getAction method of the
+HttpEnvironment object passed to the sitemap engine as described above (see
+"session-invalidator" action).</p><p>The screen-navigation action is always called because it has knowledge about
+the flow/sequence of pages and it knows how/where the preceding actions stores
+their execution status (ie. as an request attribute). Depending on those stati
+the screen-navigation action sets up a Map with an element called "nextpage"
+with the value of the page that produces the next "view".</p><p>However, one is not limited to specify distinct values at the action
+attribute. It is possible and I think useful to mark several actions with the
+same action attribute value which will then be called in sequence. This allows
+you to choose a granularity of your actions at will.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1375_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Matchers and Selectors</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Matchers and Selectors</h1><h1>Introduction</h1><p>Matchers and selectors are sitemap components. They are used to determine the
+flow, the other components involved and their ordering of the request
+processing. One particular matcher you're probably familiar with, is the
+WildcardURIMatcher. That is the one that determines the (sub-)pipeline in the
+welcome example. But there are many more matchers supplied with Apache Cocoon,
+one matches the requested URI on regular expressions, others match the client's
+hostname, existence of parameters and so on.</p><p>There is also a number of selectors supplied with Cocoon. Selectors test a
+generally simple boolean expression and allow to select on roughly the same
+things as matchers would. There is a selector on the client's hostname, on the
+client's browser etc.</p><p>To make things even more complicated, actions have very similar properties.
+You can nest other sitemap elements in an action and those are included in the
+processing only if the action completes successfully.</p><h1>So what are the differences?</h1><p>The basic structure of a selector is that of a case, switch or
+if-elseif-...-elseif-else statement in programming languages while matchers and
+actions compare more to a if statement. In addition selectors don't communicate
+the basis for their decision to the embedded elements, just select the next
+part(s) of the pipeline. Matchers and actions, however, add a new map to the
+environment that can be used for the further processing in the sub pipeline.
+</p><p>You've already come across this feature on the example sitemap: The value
+matched by the WildcardURIMatcher is used to determine the filename
+<tt>docs/samples/xsp/{1}.xsp</tt>. Here <tt>{1}</tt> represents the value that
+is stored in the environmental map with the key <tt>1</tt>. The name of the key
+is arbitrary and set by the matcher. If you had supplied a more complex pattern,
+there would be others. For example <tt>&lt;map:match
+pattern="*/*/*/*/report.html"&gt;</tt> would result in keys <tt>1</tt>,
+<tt>2</tt>, <tt>3</tt>, and <tt>4</tt> being defined, corresponding to the
+<tt>*</tt>s in the pattern.</p><p>BTW you cannot access those maps from your XSP. Use parameters to the
+generator to explicitly send them. On your XSP you can access them through an
+object called <tt>parameters</tt>. Example</p><pre>&lt;map:match pattern="*/*/*/*/report.html"&gt;
+   &lt;map:generate type="serverpages" src="docs/getPostcodeData.xsp"&gt;
+      &lt;parameter name="postcode" value="{1}{2} {3}{4}"/&gt;
+   &lt;/map:generate&gt;
+   &lt;map:transform src="stylesheets/html/report.xsl"/&gt;
+   &lt;map:serialize/&gt;
+&lt;/map:match&gt;
+
+</pre><p>On your XSP do</p><pre>&lt;xsp:expr&gt;parameters.getParameter("postcode")&lt;/xsp:expr&gt;
+
+</pre><p>Generally, one could say that selectors are better suited if the decisions
+has few easily distinguishable cases, the map feature is not needed and the
+decision occurs later in the pipeline. Their implementation should be
+lightweight and so is their integration in the compiled sitemap.</p><p>Matchers are often the very first element in a pipeline. They direct the
+processing based on more complex decision process. They are general purpose but
+more costly than selectors.</p><p>Actions should be used to <em>"do"</em> something, not to chose between
+different sub pipelines. That should be done only, if an error occurred and you
+cannot continue the regular pipeline. Of course this is a fuzzy criterion and
+using an action to choose between exactly two sub pipelines is a very common
+task i.e. for authentication. Also, often actions have no nested elements and
+the further processing is not affected by the result of the action.</p><h1>Using Matchers</h1><p>Like every other sitemap component, matchers need to be declared in the
+sitemap:</p><pre>&lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
+  &lt;map:components&gt;
+   ...
+
+   &lt;map:matchers default="wildcard"&gt;
+     &lt;map:matcher name="wildcard"
+               src="org.apache.cocoon.matching.WildcardURIMatcher"/&gt;
+     ...
+     &lt;map:matcher name="next-page"
+     src="org.apache.cocoon.matching.WildcardRequestParameterMatcher"&gt;
+        &lt;map:parameter name="parameter-name" value="next-state"/&gt;
+     &lt;/map:matcher&gt;
+   &lt;/map:matchers&gt;
+
+  ...
+  &lt;/map:components&gt;
+
+&lt;/map:sitemap&gt;
+
+</pre><p>Matchers are given a short name (e.g, "wildcard") and of course the name of
+the JAVA class that implements the matcher. In addition, parameters can be
+defined as well.</p><p>One matcher may be defined as default matcher, so whenever a matcher appears
+in the sitemap without explicit type specification it will be assumed that it is
+of the default type.</p><p>In a pipeline use the matcher like this</p><p>Matchers can be nested:</p><pre>&lt;map:match type="sessionstate" pattern="edit*"&gt;
+  &lt;!-- here you could insert parameters for the above matcher --&gt;
+  &lt;map:parameter name="attribute-name" value="__sessionstate"/&gt;
+
+  &lt;map:match type="next-page" pattern="ok*"&gt;
+    &lt;!-- do something here, eg. database updates --&gt;
+    &lt;map:call resource="simple-page1"/&gt;
+  &lt;/map:match&gt;
+  &lt;map:match type="next-page" pattern="delete*"&gt;
+    &lt;!-- do something different here, eg. database deletions --&gt;
+    &lt;map:call resource="simple-page1"/&gt;
+  &lt;/map:match&gt;
+&lt;/map:match&gt;
+
+</pre><h1>Using Selectors</h1><p>As said above, selectors are very similar to matchers. Again, you need to
+declare selectors in the sitemap.xmap</p><pre>&lt;map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"&gt;
+  &lt;map:components&gt;
+   ...
+  &lt;map:selectors default="browser"&gt;
+   &lt;map:selector name="browser"
+     src="org.apache.cocoon.selection.BrowserSelector"&gt;
+    &lt;browser name="explorer" useragent="MSIE"/&gt;
+    &lt;browser name="lynx" useragent="Lynx"/&gt;
+    &lt;browser name="netscape" useragent="Mozilla"/&gt;
+   &lt;/map:selector&gt;
+   &lt;map:selector name="parameter"
+     src="org.apache.cocoon.selection.ParameterSelector"/&gt;
+  &lt;/map:selectors&gt;
+
+  ...
+  &lt;/map:components&gt;
+
+
+&lt;/map:sitemap&gt;
+
+</pre><p>Their use is a bit different to matchers, though:</p><p>Obviously, this could have been done with matchers as well. Decide on
+yourself, what appears clearer to you in a specific situation.</p><h1>Write Your Own Matchers and Selectors</h1><section name="Matchers" style="background:none;padding:0;"/><p>Since the basic structure and the assumptions are very similar, we look first
+at matchers and point out the differences to selectors at the end.</p><p>Matchers need to implement the <tt>org.apache.cocoon.matching.Matcher</tt>
+interface. See javadocs for more details, see also example matchers included in
+the distribution.</p><p>If you would like to do global configuration for your matcher, it has to
+implement the <tt>org.apache.avalon.framework.configuration.Configurable</tt>
+interface.</p><p>Local configuration parameters are avalon parameters and thus can be easily
+read and used with the generated matcher method.</p><p>If the matcher returns not null, the match was successful and the nested sub
+pipeline is executed. Components in sub pipeline can access the matching result
+through the returned map.</p><p>The easiest way to write your own matcher would be to base it upon
+org.apache.cocoon.matching.WildcardURIMatcher and override the getMatchString
+method with your own.</p><section name="Selectors" style="background:none;padding:0;"/><p>Selectors and selector factories differ from their matcher counter parts only
+in the fact that selectors return boolean values rather than maps. Thus when a
+selector returns <tt>true</tt> the nested elements will be included in the
+processing, otherwise they are not included. Since no map is returned, no
+additional information may be passed to those elements.</p><p>For selectors, the last argument reads <tt>param</tt> instead of
+<tt>parameters</tt>.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1376_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Modules</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Modules</h1><p>TBD</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1377_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml?rev=1329674&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml Tue Apr 24 12:33:07 2012
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+      Licensed to the Apache Software Foundation (ASF) under one
+      or more contributor license agreements.  See the NOTICE file
+      distributed with this work for additional information
+      regarding copyright ownership.  The ASF licenses this file
+      to you 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.
+    --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Core - Redirection</title><author email="cocoon-docs@apache.org">Apache Cocoon Documentation Team</author></properties><body>
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Redirection</h1><h1>Introduction</h1><p>A Redirector allows the sitemap to pass a request for one URI on to another,
+whether that other URI is handled by Cocoon or not.</p><p>To redirect from <tt>page1.html</tt> to <tt>page2.html</tt>, you can use the
+following:</p><pre>  &lt;map:match pattern="page1.html"&gt;
+    &lt;map:redirect-to uri="page2.html"/&gt;
+  &lt;/map:match&gt;
+
+        </pre><h1>HTTP redirects and how they work</h1><p>If the URI specified does not use the Cocoon: protocol, then an HTTP redirect
+will occur. The new URI is sent back to the client, which will then request the
+page from this new location.</p><p>Therefore, directory handling in redirect URIs works differently from other
+sitemap components.</p><p>If the new URI is relative, then it will be relative to the directory of the
+page that called it, not relative to the URI of the sitemap containing it. Thus,
+the following is incorrect:</p><pre>  &lt;map:match pattern="folder/page1.html"&gt;
+    &lt;map:redirect-to uri="folder/page2.html"/&gt;
+  &lt;/map:match&gt;
+
+</pre><p>This will in fact redirect the user to folder/folder/page2.html, which is
+probably not intended. The correct version is:</p><pre>  &lt;map:match pattern="folder/page1.html"&gt;
+    &lt;map:redirect-to uri="page2.html"/&gt;
+  &lt;/map:match&gt;
+    
+</pre><h1>Internal Redirects Using the Cocoon Protocol</h1><p>A redirection URI can make use of the <tt>cocoon:</tt> protocol to return
+content from another Cocoon pipeline. In this case, the redirection happens
+internally. The content from the redirected URI is returned to the client as if
+it came from the original URI.</p><p>Directory handling is the same here as for other sitemap components. So that:
+</p><pre>  &lt;map:match pattern="folder/page1.html"&gt;
+    &lt;map:redirect-to uri="cocoon:/folder/page2.html"/&gt;
+  &lt;/map:match&gt;
+
+</pre><p>will return the content of <tt>page2.html</tt> to the client in response to
+the request for <tt>page1.html</tt>.</p><p>Note: when the <tt>cocoon:</tt> protocol is used, an HTTP redirect is not
+used.</p><h1>Session Management with Redirects</h1><p>By setting the <tt>session</tt> attribute to <tt>yes</tt>, the current
+session will be maintained during the redirect.</p><h1>Temporary and Permanent Redirects</h1><p>By default, an HTTP redirect sends a code of <tt>SC_MOVED_TEMPORARILY</tt>,
+(<tt>302</tt>). This instructs the user agent to use the new URI, but not to
+cache the resulting page, as it may well soon revert back to the old URI.</p><p>This can be a problem for pages that have been moved permanently, as the new
+page will never be cached, placing additional load on both the browser and on
+the server.</p><p>This can be avoided using a permanent redirect, using a code of
+<tt>SC_MOVED_PERMANENTLY</tt> (<tt>301</tt>). A permanent redirect can be
+specified as:</p><pre>  &lt;map:match pattern="page1.html"&gt;
+    &lt;map:redirect-to uri="page2.html" permanent="yes"/&gt;
+  &lt;/map:match&gt;
+
+        </pre><p>This results in the user agent caching the redirected page, and thus saves
+resources both on the server and for the client's browser.</p><h1>Redirects in Pipelines</h1><p>A redirect must stand alone in a pipeline - it cannot occur after a
+generator. If a redirect needs to be generated conditionally by a pipeline, then
+a <tt>&lt;meta&gt;</tt> tag redirect should be added into the
+<tt>&lt;head&gt;</tt> of the HTML page. The syntax for this is:</p><pre>  
+&lt;html&gt;
+  &lt;head&gt;
+    &lt;meta http-equiv="refresh" content="0;URL=page2.html"/&gt;
+    ...
+  &lt;/head&gt;
+  ...
+&lt;/html&gt;
+
+        </pre><h1>Global Redirects</h1><p>When an aggregator accesses a source that includes a redirection, it will
+aggregate the document specified by the redirection URI.</p><p>Alternatively, if a redirection that has the <tt>global</tt> attribute is set
+(to <tt>yes</tt> or <tt>true</tt>) occurs within an aggregation, the aggregation
+is cancelled and the redirect is sent back to the client.</p><h1>Redirecting to Resources</h1><p>Specifiying a <tt>resource</tt> attribute allows the redirection to a sitemap
+resource. This usage has been deprecated. <tt>map:call</tt> should be used
+instead.</p></div></div>
+       </body></document>
\ No newline at end of file

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml
------------------------------------------------------------------------------
    svn:keywords = Date Revision Author HeadURL Id

Propchange: cocoon/trunk/site/cocoon-core-site/core/2.2/src/site/xdoc/1378_1_1.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml



Mime
View raw message