Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml Mon Apr 23 14:58:36 2012
@@ -0,0 +1,200 @@
+<?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 2.2 Site - How to configure consistent encoding in Cocoon</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to configure consistent encoding in Cocoon</h1><p>The best for internationalization, ie. support of umlauts, special
+characters, non-english languages, is to handle everything in UTF-8, because
+this is probably the most intelligent encoding available out there.</p><div class="note"><div><strong>Note: </strong>If you need another encoding, simply replace all occurrences of
+UTF-8 with that one, but note that this guide was only tested with UTF-8, other
+encodings might not be supported at all places.</div></div><p>The following how-to covers the typical steps to achieve a consistent
+encoding throughout a Cocoon application. Some <a href="#theory">Background
+information</a> can be found at the end of this page.</p><h1>1. Sending all pages in UTF-8</h1><p>You need to configure Cocoon's serializers to UTF-8. The XML serializer
+(<tt><serialize type="xml" /></tt>) and the HTML serializer
+(<tt><serialize type="html" /></tt>) need to be configured. To support all
+browsers, you must state the encoding to be used for the body and also include a
+meta tag in the html:
+<tt><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></tt>.
+This is very important, since the browser will then send form requests encoded
+in UTF-8 (and browsers normaly don't mention the encoding in the request, so you
+have to assume they are doing it right). Here is the configuration for the
+serializer components for your sitemaps that will do that:</p><pre><serializer name="xml" mime-type="text/xml"
+ src="org.apache.cocoon.serialization.XMLSerializer">
+ <encoding>UTF-8</encoding>
+</serializer>
+
+<serializer name="html" mime-type="text/html; charset=UTF-8"
+ src="org.apache.cocoon.serialization.HTMLSerializer">
+ <encoding>UTF-8</encoding>
+
+ <!-- the following common doctype is only included for completeness, it has no impact on encoding -->
+ <doctype-public>-//W3C//DTD HTML 4.01 Transitional//EN</doctype-public>
+ <doctype-system>http://www.w3.org/TR/html4/loose.dtd</doctype-system>
+</serializer>
+</pre><h1>2. AJAX Requests with CForms/Dojo</h1><p>If you use CForms with ajax enabled, Cocoon will make use of dojo.io.bind()
+under the hood, which creates XMLHttpRequests that POST the form data to the
+server. Here Dojo decides the encoding by default, which does not match the
+browser's behaviour of using the charset defined in the META tag. But you can
+easily tell Dojo which formatting to use for all dojo.io.bind() calls, just
+include that in the top of your HTML pages, before dojo.js is included:</p><pre><script>djConfig = { bindEncoding: "utf-8" };</script>
+</pre><p>You might already have other djConfig options, then simply add the
+<tt>bindEncoding</tt> property to the hash map.</p><h1>3. Decoding incoming requests: Servlet Container</h1><p>When the browser sends stuff to your server, eg. form data, the
+<tt>ServletRequest</tt> will be created by your servlet container, which needs
+to decode the parameters correctly into Java Strings. If there is the encoding
+specified in the HTTP request header, he will use that, but unfortunately this
+is typically not the case. When the browser sends a form post, he will only say
+<tt>application/x-www-form-urlencoded</tt> in the header. So you have to assume
+the encoding here, and the right thing to assume is the encoding of the page you
+originally sent to the browser.</p><p>The servlet standard says that the default encoding for incoming requests
+should be ISO-8859-1 (Jetty is not according to the standard here, it assumes
+UTF-8 by default). So to make sure UTF-8 is used for the parameter decoding, you
+have to tell your servlet that encoding explicitly. This is done by calling
+<tt>ServletRequest.setCharacterEncoding()</tt>. To do that for all your
+requests, you can use a servlet filter like this one:
+<a href="http://wiki.apache.org/cocoon/SetCharacterEncodingFilter">SetCharacterEncodingFilter</a>.
+Put this into one of your Cocoon blocks under
+<tt>src/main/java/my/package/filters/SetCharacterEncodingFilter</tt> so that the
+class will be in a jar that lands in <tt>WEB-INF/lib</tt> and thus being
+availble for use in the web.xml configuration.</p><p>Then you add the filter to the web.xml:</p><pre><filter>
+ <filter-name>Set Character Encoding</filter-name>
+ <filter-class>my.package.filters.SetCharacterEncodingFilter</filter-class>
+ <init-param>
+ <param-name>encoding</param-name>
+ <param-value>UTF-8</param-value>
+ </init-param>
+</filter>
+
+<!-- either mapping to URL pattern -->
+
+<filter-mapping>
+ <filter-name>Set Character Encoding</filter-name>
+ <url-pattern>/*</url-pattern>
+</filter-mapping>
+
+<!-- or mapping to your Cocoon servlet (the servlet-name might be different) -->
+
+<filter-mapping>
+ <filter-name>SetCharacterEncoding</filter-name>
+ <servlet-name>CocoonBlocksDispatcherServlet</servlet-name>
+</filter-mapping>
+
+</pre><p>Since the filter element was added in the servlet 2.3 specification, you need
+at least 2.3 in your web.xml, but using the current 2.4 version is better, it's
+the standard for Cocoon webapplications. For 2.4 you use a XSD schema:</p><pre><web-app version="2.4"
+ xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
+</pre><p>For 2.3 you need to modify the DOCTYPE declaration in the web.xml:</p><pre><!DOCTYPE web-app
+ PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+</pre><h1>4. Setting Cocoon's encoding (especially CForms)</h1><p>To tell Cocoon to use UTF-8 internally, you have to set 2 properties:</p><pre>org.apache.cocoon.containerencoding=utf-8
+org.apache.cocoon.formencoding=utf-8
+</pre><p>They need to be in some <tt>*.properties</tt> file under
+<tt>META-INF/cocoon/properties</tt> in one of your blocks. Note that the
+containerencoding must be the same as the one you specified in the
+SetCharacterEncodingFilter. But here we are using UTF-8 everywhere anyway.</p><h1>5. XML Files</h1><p>This is normally not a problem, since the standard encoding for XML files is
+UTF-8. However, they should always start with the following instruction, which
+should force your XML Editor to save them in UTF-8 (it looks like most of them
+do that, so there should not be a problem here).</p><pre><?xml version="1.0" encoding="UTF-8"?>
+</pre><h1>6. Special Transformers</h1><p>The standard XSLT Transformers and others are working on SAX events, which
+are not serialized, thus encoding is not a problem. But there are some special
+transformers that pass stuff on to another library that does include
+serialization and might need a hint to use the correct encoding. One problem is
+for example the NekoHTMLTransformer:
+<a href="https://issues.apache.org/jira/browse/COCOON-2063">https://issues.apache.org/jira/browse/COCOON-2063</a>.
+</p><p>If you think there might be a transformer doing things wrong in your
+pipeline, add a <tt>TeeTransformer</tt> between each step, outputting the XML
+between the transformers into temp1.xml, temp2.xml and so on to look for the
+place where your umlaute and special characters are messed up.</p><h1>7. Your own XML serializing Sources</h1><p>If you have your own Source implementation that needs to serialize XML, make
+sure it will do that in UTF-8 as well. A good idea is to use Cocoon's XML
+serializer, since we already configured that one to UTF-8 above. Sample code
+that does that is here:
+<a href="http://wiki.apache.org/cocoon/UseCocoonXMLSerializerCode">UseCocoonXMLSerializerCode</a>
+</p><h1>Further information</h1><section name="Browser encoding basics" style="background:none;padding:0;"/><h3>Getting pages</h3><p>If your Cocoon application needs to read request parameters that could
+contain <em>special</em> characters, i.e. characters outside of the first 128
+ASCII characters, you'll need to pay attention to what encoding is used.</p><p>Normally a browser will send data to the server using the same encoding as
+the page containing the submitted form (or whatever). So if the pages are
+serialized using UTF-8, the browser will submit form data using UTF-8. The user
+can change the encoding, but it's quite safe to assume he/she won't do that
+(have you ever done it?).</p><p>The browser will either read the encoding from either the <meta> tag
+inside the HTML <head>:</p><pre><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</pre><p>or from the HTTP Header Content-Type:</p><pre>Content-Type: text/html; charset=UTF-8
+</pre><p>One has to include both to support all browsers. This will be done by the
+HTML serializer if you configure it with the parameters mime-type and encoding,
+as stated above.</p><h3>Sending form data</h3><p>By default, if the browser doesn't explicitely mention the encoding, a
+servlet container will decode request parameters using the ISO-8859-1 encoding
+(independent of the platform on which the container is running). So in the above
+case where UTF-8 was used when serializing, we would be facing problems. An
+exception, that might hide the problem and which you will face when you use the
+handy mvn jetty:run to run your Cocoon application, is that Jetty uses UTF-8 by
+default. It does not adhere to the servlet container standard here.</p><p>You either have to configure your container with the default encoding you
+want (e.g. UTF-8), if that is possible, or you must use a servlet-filter
+solution like the
+<a href="http://wiki.apache.org/cocoon/SetCharacterEncodingFilter">SetCharacterEncodingFilter</a>.
+Using a servlet filter also has the advantage that it will work for any servlet.
+Suppose your webapp consists of multiple servlets, with Cocoon being only one of
+them. Sometimes the processing could start in another servlet (which sets the
+character encoding correctly) and then be forwarded to Cocoon, while other times
+the processing could start immediately in the Cocoon servlet. It would then be
+impossible to know in Cocoon whether the request parameter encoding needs to be
+corrected or not (see below).</p><section name="Request parameter decoding in Cocoon" style="background:none;padding:0;"/><h3>Fixing a wrong servlet container</h3><p>If you are not able to set the default encoding for your servlet container to
+what you actually want, it is possible to configure Cocoon to re-decode
+parameters properly. Suppose the servlet container has ISO-8859-1 default
+encoding set, but the requests from the browser are actually encoded in UTF-8.
+Then you can configure Cocoon with these properties:</p><pre>org.apache.cocoon.containerencoding=iso-8859-1
+org.apache.cocoon.formencoding=utf-8
+</pre><p>For Java-insiders: what Cocoon actually does internally is apply the
+following trick to get a parameter correctly decoded: suppose "value" is a
+string containing a request parameter, then Cocoon will do:</p><pre>value = new String(value.getBytes("ISO-8859-1"), "UTF-8");
+</pre><p>So it recodes the incorrectly decoded string back to bytes and decodes it
+using the correct encoding. The first (ISO-8859-1 in the example) is the
+containerencoding, the second one the formencoding.</p><p>Not that this only works for core Cocoon concepts, eg. sitemaps, CForms and
+others accessing the request parameters. There are other components, eg. the
+JSPGenerator, that access the original HttpServletRequest object and thus do not
+get the correctly re-decoded parameter values (that is, if for example the JSP
+page itself would read request parameters). The only working solution seems to
+be the servlet-filter here.</p><h3>Locally overriding the form-encoding</h3><p>Cocoon is ideally suited for publishing to different kinds of devices, and it
+may well be possible that for certain devices, it is required to use different
+encodings. In this case, you can redefine the form-encoding for specific
+pipelines using the SetCharacterEncodingAction.</p><p>To use it, first of all make sure the action is declared in the map:actions
+element of the sitemap:</p><pre><map:action name="set-encoding" src="org.apache.cocoon.acting.SetCharacterEncodingAction"/>
+</pre><p>and then call the action at the required location as follows:</p><pre><map:act type="set-encoding">
+ <map:parameter name="form-encoding" value="some-other-encoding"/>
+</map:act>
+</pre><section name="Operating System Preliminaries" style="background:none;padding:0;"/><p>Not having influence on request parameter decoding, but sometimes making
+trouble with text files, database communication, etc. are operating system
+language settings. Working with non-english characters may pose problems, as the
+JVM seems to detect the system language. If, e.g., german umlauts should be
+correctly processed with Cocoon on Linux, it is required to set the LANG
+environment variable to de like this:</p><p><tt>export LANG=de</tt></p><p>That's one of several ways of setting the JVM locale, see also
+<a href="http://wiki.apache.org/cocoon/SettingTheJvmLocale">SettingTheJvmLocale</a>.
+</p><section name="More readings" style="background:none;padding:0;"/><ul>
+<li>
+
+<a href="http://marc.theaimsgroup.com/?t=106760662600010&r=1&w=2">Cocoon's
+defaults form-encoding and seerialize-encoding</a>
+<a href="http://wiki.apache.org/cocoon/MarcPortier">MarcPortier</a> proposal to
+remove inconsitencies in the way Cocoon handles the encoding of serialized text
+and request-parameter decoding.
+<a href="http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106772461923197&w=2">This</a>
+is a good summary of the thread.
+</li>
+<li>Cocoon does not support the HTTP request header
+<a href="http://www.w3.org/TR/REC-html40/interact/forms.html#adef-accept-charset">Accept-Charset</a>,
+where the browser specifies a list of encodings it can handle. Maybe this might
+be useful to implement.</li>
+</ul></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1366_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml Mon Apr 23 14:58:36 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 2.2 Site -</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">2.1 to 2.2 migration</h1><p>TODO</p></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1402_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml Mon Apr 23 14:58:36 2012
@@ -0,0 +1,107 @@
+<?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 2.2 Site - New in 2.2</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">New in 2.2</h1><p>While developing Cocoon 2.2 the main goal was simplicity, modularity and
+consistent configuration. This page is a summary of all the new features and
+improvements.</p><h1>General</h1><ul>
+<li>Cocoon 2.2 doesn't use an Avalon-based component manager any more but uses
+Spring 2 instead.</li>
+<li>Cocoon components (sitemap components as well as general components) can be
+defined as Spring beans now. This brings all the power of Spring (Dependency
+Injection, AOP framework, etc.) to the core of Cocoon without having to rely on
+some kind of bridging mechanism. Avalon component configurations are still
+supported but deprecated.</li>
+<li>Cocoon core has been split up into a bunch of smaller modules (pipeline
+api/impl, sitemap api/impl, components, etc.). This is an important step in
+order to make Cocoon more easily embeddable in the future and to define clear
+contracts.</li>
+<li>An optional additional validation of sitemaps based on an XML schema
+definition is configureable.</li>
+<li>Cocoon 2.2 uses Comons Logging instead of Avalon Logkit as logging interface
+and Log4j as logging implementation. (<em>Also see the 'Incompatibles changes'
+section of this document.</em>)</li>
+</ul><h1>Modularity</h1><ul>
+<li>In order to make Cocoon applications more modular, the
+Servlet-Service-Framework was introduced. The Servlet-Service-Framework is a
+general-purpose framework that makes it possible to establish contracts between
+sub-applications.</li>
+<li>The Servlet-Service-Framework introduces polymorphic relationships between
+services.</li>
+<li>The Servlet-Service-Framework has no dependency on the 'traditional' Cocoon
+(sitemap/pipeline machinery) and can be used together with any
+JavaServlet-compatible web application.</li>
+</ul><h1>Configuration and Deployment</h1><ul>
+<li>Cocoon 2.1 was configured at build time. This means that you have to build
+Cocoon 2.1 yourself in order to get the Cocoon that you need for your
+application. There was no simple upgrade path from one minor/patch release to
+the next. Cocoon 2.2 expands the meaning of blocks. Blocks have become binary
+deployment units which follow a particular directory structure and can provide
+Servlet-Services, Java services, Java classes and resources and Cocoon specific
+files (templates, stylesheets, etc.).</li>
+<li>Cocoon blocks express their dependencies using project object model
+descriptors (POM 4.0) defined by the Maven project. This makes it easy to build
+Cocoon 2.2 based projects with Maven 2 though it's no hard requirement.</li>
+<li>Cocoon 2.2 provides a consistent way of configuration based on the Cocoon
+Spring Configurator - a new Cocoon sub project. It supports the configuration of
+components based on the Spring property placeholder configurer and the property
+overrider configurer and is aware of running modes, i.e. you can provide special
+properties for different environments (e.g. development, test, production).</li>
+<li>Cocoon 2.2 uses Jakarta Commons Logging 1.1 as logging framework and Log4j
+as default implementation.</li>
+<li>The number of dependencies of a minimal Cocoon application (sitemaps,
+pipelines, XML templates) was reduced and together they amount to less than
+10MBÂ (incl. Xalan and Xerces libs!).</li>
+</ul><h1>Tools</h1><ul>
+<li>The Cocoon Maven 2 plugin makes is very easy to use Cocoon together with
+Maven 2 as build system. The main features are</li>
+<ul>
+<li>starting a block as web application (+ support for the automatical reload of
+Java classes and all other resources),</li>
+<li>rewritting web.xml to weave in a shielding classloader that reverses the
+classloading hierarchy in order to avoid classloader problems (e.g. with XML
+libraries),</li>
+<li>a block can supply xpatch files to patch the <tt>web.xml </tt>of the
+destination web application.</li>
+</ul>
+
+<li>Schema files for sitemaps.</li>
+</ul><h1>Deprecation</h1><ul>
+<li>Avalon-style component configurations</li>
+</ul><div class="fixme"><div><strong>Fixme: </strong>Deprecation is subject of an ongoing dicussion.</div></div><h1>Migrating 2.1 components</h1>When you have avalon based components that you want to use with the new
+spring configuration system make sure you are configure them right. Avalon based
+components were implementing an interface to e.g. be Threadsafe. In Spring you
+will need to configure the scope (default is singletone). If you see a lot of
+NPE in concurrency tests then you would need to use the prototype scope as shown
+below.<pre/><pre><beans>
+ <bean id="dispatcher" scope="prototype"
+ name="org.apache.cocoon.transformation.Transformer/dispatcher"
+ class="org.apache.forrest.dispatcher.transformation.DispatcherTransformer">
+ <property name="manager" ref="org.apache.avalon.framework.service.ServiceManager"/>
+ </bean>
+</beans></pre><pre/><h1>Incompatible changes</h1><ul>
+<li>All Cocoon components don't implement the Avalon Logkit logging interfaces
+(<tt><a href="http://excalibur.apache.org/apidocs/org/apache/avalon/framework/logger/Logger.html">org.apache.avalon.framework.logger.Logger</a></tt>
+) anymore but Commons logging instead. This change also makes it possible to
+configure components via Spring configuration files. If you extend one of those
+components (e.g.
+<a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/AbstractSAXTransformer.html">AbstractSAXTransformer</a>),
+you have to change the logger implementation and to recompile your classes. We
+are sorry but there is no backwards compatible way in doing this move from
+Avalon Logkit to Commons Logging.</li>
+</ul></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1420_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml Mon Apr 23 14:58:36 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 2.2 Site - Download</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Download</h1><h1>Cocoon 2.2 Core</h1><p>The current version of Cocoon 2.2Â can be found at our central
+<a href="../1284_1_1.html">download page</a>.</p><h1>Cocoon Blocks</h1><p>The download pages for each released block can be found as part of the block
+specific documentations. In order to get an overview of what blocks are
+available, use the <a href="../2.2/blocks/1204_1_1.html">list of blocks</a>.</p></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1447_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml Mon Apr 23 14:58:36 2012
@@ -0,0 +1,26 @@
+<?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 2.2 Site - Screencasts</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Screencasts</h1><h1>Cocoon reloading class Maven plug-in - rapid development</h1><p>The following screencast demonstrates how Rapid Application (Block more
+precisely) Development is achieved with <a href="../2.2/maven-plugins/maven-plugin/1.0/1295_1_1.html">Maven's RCL</a>
+(AKA Cocoon) plug-in.</p><p>Some initial steps leading to creation of a basic block are taken from
+"<a href="1159_1_1.html">Your first Cocoon application using Maven 2</a>" tutorial.
+</p><div class="note"><div><strong>Note: </strong>During the screencast old version (1.0.0-RC2) of archetype is
+being used for initial block creation. You should use always use the latest
+available version which can be checked <a href="../2.2/maven-plugins/1208_1_1.html">here</a>.</div></div><div class="includedDoc"><object height="725" width="1008" type="application/x-shockwave-flash" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0"><param name="movie" value="flash/1452_1_1.swf"/><param name="Play" value="true"/><param name="Loop" value="false"/><param name="Autoplay" value="false"/><param name="Autostart" value="false"/><embed src="flash/1452_1_1.swf" height="725" width="1008" play="true" loop="false" autoplay="false" autostart="false"/></object><br/></div></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1448_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml Mon Apr 23 14:58:36 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 2.2 Site - Test2</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Test2</h1><p>Test2</p><div class="includedDoc"><div id="contentBody"><div id="bodyText"><h1 class="docTitle">Test1</h1><p>This document has been created for testing purposes only!</p></div></div></div></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/1454_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml?rev=1329267&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml (added)
+++ cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml Mon Apr 23 14:58:36 2012
@@ -0,0 +1,60 @@
+<?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 2.2 Site - Overview</title>
+ <author email="[email protected]">Apache Cocoon Documentation Team</author>
+ </properties>
+ <body>
+ <div id="contentBody">
+ <div id="bodyText">
+ <h1 class="docTitle">Overview</h1>
+ <p>The main design goal of Apache Cocoon 2.2 was providing better support for
+ modularization:
+ </p>
+ <p>
+ <img width="473" height="341" name="cocoon22_overview" alt="cocoon22_overview" src="images/1401_1_1.img"/>
+ </p>
+ <p>Cocoon is based on the
+ <a href="http://static.springframework.org/spring/docs/2.0.x/reference/index.html">Spring
+ 2.0
+ </a> framework. The Spring Configurator and the Servlet Service Framework are
+ two subprojects having Spring as main dependency. It's important to note that
+ both can be reused outside of Cocoon Core.
+ <br/>
+ The
+ <a href="../subprojects/configuration/1.0/1329_1_1.html">Spring Configurator</a> provides basic support for
+ configuring web applications that make use of Spring. The
+ <a href="../subprojects/servlet-service/1.1/1325_1_1.html">Servlet Service Framework</a> enables modularization based
+ on the
+ <tt>javax.servlet.Servlet</tt> interface. Those servlet services are
+ <a href="http://en.wikipedia.org/wiki/Polymorphism_in_object-oriented_programming">polymorphic</a>.
+ </p>
+ <p>
+ <a href="../2.2/core-modules/1210_1_1.html">Cocoon Core</a> provides implementations of a sitemap
+ engine and of pipelines. It also establishes a contract to add modules. The unit
+ of modularization in Cocoon is called blocks.
+ <a href="../2.2/blocks/1204_1_1.html">This list</a>
+ gives an overview of what additional functionality is available. Web
+ applications based on Cocoon are also developed following the block contracts.
+ </p>
+ </div>
+ </div>
+ </body>
+</document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-22-site/src/site/xdoc/index.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.