+ + Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/site.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/site.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/site.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,46 @@ +Cocoon Maven 2 Plugin - Shielded ClassloadingApache Cocoon Documentation Team +

Shielded Classloading

Shielded classloading is an optional feature of the Cocoon deployer-plugin +for Maven. It helps you in avoiding typical problems with respect to class +loading. Usually the servlet container sets up a class loader for each web +application. This class loader works "parent-first" which means that whenever a +class is loaded it is first searched in the parent class loader of the web +application class loader and only if its not available there, it is loaded from +the classes in WEB-INF/classes or the jars in WEB-INF/lib. In general this is a +useful mechanism which also allows you to share classes between web applications +by putting them in the parent class loader (refer to the documentation of your +application server/servlet engine for more information).

Unfortunately there are some problems with this approach: for example if the +servlet engine has configured a logging framework like commons logging and +exposes thisÂ in the parent class loader for the web applications, than all web +applications have to use this configuration and are not able to use their own. +Even more important is the used XSLT processor (and some other stuff contained +in the endorsed directory). By default you always use the XSLT processor shipped +with the JDK; you can override this by specifying one using the endorsed +mechanism but in many cases you can't use this way. As the XSLT processor +shipped with the JDK has some bugs it is advisable to use the latest version. +

The only reliable way of avoiding all these class loading issues is to use a +mechanism we call shielded class loading: the web application uses its own class +loader which works "parent-last". In this case classes are always tried to be +loaded from the WEB-INF/classes or WEB-INF/lib directory first. Through this +mechanism you can enforce the use of the XSLT processor you want for your +application, of the logging configuration you need etc.

Some application servers provide a configuration for this, but you can also +use some of the functionality provided by Cocoon: if you are using the Cocoon +deploy plugin with Maven 2, this plugin rewrites your web.xml to use the +shielded class loader.

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1262_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,89 @@ +Cocoon Maven 2 Plugin - Using the Reloading ClassloaderApache Cocoon Documentation Team +

Using the Reloading Classloader

These instructions should work with any Cocoon block. The sample +configurations are based on the Getting Started guide. +

Step 1: Enable the plugin in pom.xml

In the pom.xml you have to add the plugin:

<project>
+  <build>
+    <plugins>
+      [...]
+      <plugin>
+        <groupId>org.apache.cocoon</groupId>
+        <artifactId>cocoon-maven-plugin</artifactId>
+        <version>1.0.0-M2</version>
+     Â </plugin>
+      [...]
+    </plugins>
+  </build>
+</project>   
+

Step 2: Configure the plugin

You can also provide configuration properties. Use the +goal documentation generated from the Javadoc +comments to find out more.

The central configuration file is rcl.properties which has to be put into the +root directory of the block that you want to run, e.g.

com.mycompany.myBlock1.block%classes-dir=./target/classes

The property names consist of the name of the block servlet which is the +unique name of the Spring bean + %classes_dir . The value is the +relative or absolute filesystem path.

Step 3: Invoke the plugin

The Maven 2 plugin can be invoked by calling

mvn cocoon:prepare

This creates a web application into ./target/rcl/webapp for your +block.

If you want to avoid this additional step, you can invoke it automatically, +e.g. by

If you want to invoke it automatically, add it to the execution section of +your plugin definition, e.g.

<plugin>
+  <groupId>org.apache.cocoon</groupId>
+  <artifactId>cocoon-maven-plugin</artifactId>
+  <version>1.0.0-M2</version>
+  <executions>
+    <execution>
+      <phase>compile</phase>
+      <goals>
+        <goal>prepare</goal>
+      </goals>
+    </execution>
+  </executions>       
+</plugin>
+

Step 4: Create Eclipse project files

Move to getting-started-app/ and invoke

mvn eclipse:eclipse

and import the new Eclipse project into your Eclipse workspace.

Step 5: Start the servlet container

Now you can configure the Maven 2 Jetty plugin to use the web application +that was created by the block in target/rcl/webapp:

<project>
+  <build>
+    <plugins>
+      [...]
+      <plugin>
+        <groupId>org.mortbay.jetty</groupId>
+        <artifactId>maven-jetty-plugin</artifactId>
+        <version>6.1.7</version>
+        <configuration>
+          <connectors>
+            <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
+              <port>8888</port>
+              <maxIdleTime>30000</maxIdleTime>
+            </connector>
+          </connectors>
+          <webAppSourceDirectory>${project.build.directory}/rcl/webapp</webAppSourceDirectory>
+          <contextPath>/</contextPath>
+          <systemProperties>
+            <systemProperty>
+              <name>org.apache.cocoon.mode</name>
+              <value>dev</value>
+            </systemProperty>
+          </systemProperties>
+        </configuration>
+      </plugin>
+      [...]
+    </plugins>
+  </build>
+</project>  Â

Call mvn jetty:run and point your browser to +http://localhost:8888/block1/ inÂ your browser.

There is a tutorial that describes how to debug +Cocoon.

Step 6: Change a class file

Now it's time to see the reloading classloader in action. Open +getting-started-app/myBlock1/src/main/java/com/mycompany/??? and change +it. Refresh your browser and you should see the changed values there.

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1297_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,38 @@ +Cocoon Maven 2 Plugin - rcl.propertiesApache Cocoon Documentation Team +

rcl.properties

Location

The default location of rcl.properties is at the root directory of +your block, next to pom.xml.

What can be configured?

Syntax

[name-of-the-block]%classes-dir=[path-to-a-blocks-classes-dir]

Examples

com.mycompany.app.block%classes-dir=./target/classes
com.mycompany.app.block2%classes-dir=C:/test/block2/target/classes +

Syntax

%classes-dir=[path-to-a-library] +%exclude-lib=[groupId]:[artifactId]

Example

%classes-dir=C:/test/mylib/target/classes +

Note: You can use the %classes-dir and %exclude-lib +properties as often as you need in your properties file

All other properties are either interpreted as Cocoon +properties or Spring bean properties. The +differenciation is done whether the property contains a "/" character. If so, it +is considered as Spring bean configurator property.

Variables interpolation and includes

As this configuration file is managed by +Apache Commons +Configuration you can benefit from all the features it provides. The two +most important ones are +variables +interpolation and +includes. +

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1298_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,41 @@ +Cocoon Maven 2 Plugin - Using the Cocoon DeployerApache Cocoon Documentation Team +

Using the Cocoon Deployer

Step 1: Basics

In order to use the Cocoon Deployer, you need a Cocoon web application, e.g. +one that is generated as described in the Getting Started +Tutorial. Expressed in terms of Maven 2, it mean that the packaging +type in your pom.xml is war.

Step 2: Enabling the deployer

Enable the Cocoon Maven plugin in your pom.xml:

<project>
+  <build>
+    <plugins>
+      [...]
+      <plugin>
+        <groupId>org.apache.cocoon</groupId>
+        <artifactId>cocoon-maven-plugin</artifactId>
+        <version>1.0.0-M2</version>
+        <configuration>
+          [...]
+        </configuraiton>
+      </plugin>
+      [...]
+    </plugins>
+  </build>
+</project>

Step 3: Configuration

You can also provide configuration properties. Use the +goal documentation generated from the Javadoc +comments to find out more.

Step 4: Invoke the deployer

Finally you have to invoke the plugin. If you want to do this manually, enter +

mvn cocoon:deploy

mvn cocoon:deploy-war

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1358_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,39 @@ +Cocoon Maven 2 Plugin - PurposeApache Cocoon Documentation Team +

Purpose

If you develop your Cocoon applications based on blocks, you will come to the +point that you want to run it while you are working on its resources. The +reloading classloader goal creates a minimal web application that you can use in +any servlet container.

This web application automatically detects changes in

src/main/java
src/main/resources
src/main/resources/COB-INF
src/main/resources/META-INF

This means that any changes in

Cocoon resources (sitemaps, templates, form definitions, flowscripts, etc.) +
Java classes and resources
Components (Spring beans and Avalon concepts)

are detected and will take effect nearly immediatly. Because of the use of +the Jakarta Commons JCI, you can also change the signatures of your classes and +methods.The plugin also enables you to use other blocks in a the +reloading mode together with the block that you apply the reloading classloader +plugin on.Finally, the plugin also supports the patching mechanism +that comes with the deployer goal. By using it, your blocks can contain parts of +the web.xml, e.g. a servlet configuration.

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1359_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,82 @@ +Cocoon Maven 2 Plugin - XPatchApache Cocoon Documentation Team +

XPatch

The xpatch mechanism enables you to split up your web.xml and put the +snippets into the block it belongs too. It takes all *.xweb files from +src/main/resources/META-INF/cocoon/xpatch and applies them to the +generated web.xml file that you will find in +target/rcl/webapp/WEB-INF/web.xml.

Here is an example of an xweb file:

<xweb xpath="/web-app" 
+      unless="comment()[contains(., 'Xindice XML-RPC Server servlet configuration')]" 
+      insert-after="servlet[last()]">
+
+  <!-- XMLDB Block, Xindice XML-RPC Server servlet configuration -->
+  <servlet>
+    <servlet-name>Xindice</servlet-name>
+    <display-name>Xindice XML-RPC Server</display-name>
+    <servlet-class>org.apache.xindice.server.XindiceServlet</servlet-class>
+    <init-param>
+      <param-name>xindice.configuration</param-name>
+      <param-value>WEB-INF/xindice.xml</param-value>
+    </init-param>
+    <load-on-startup>1</load-on-startup>
+  </servlet>
+  
+</xweb>
+

This xweb file adds the Xindice-RPC Server servlet to your web.xml.

Syntax

+ + + + + + + + + + + + + + + + + + + + + +

+	+ description +
+ xweb +	+ That's the root element. Everything it contains will be applied. +
+ @xpath +	+ The xpatch within web.xml where the xweb snippet should be applied to. +
+ @unless +	+ A condition when the patch should NOT be applied. +
+ @insert-after +	+ Define the exact position within result of the xpath. +

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1360_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,29 @@ +Cocoon Maven 2 Plugin - PurposeApache Cocoon Documentation Team +

Purpose

The Cocoon Deployer goal provides two features that rewrite a web application +in order to add functionality that comes from

reversing the classloader hierarchy
+By reversing the classloader hierarchy you can make sure that the dependencies +you define are found first before the classpath of the application server is +searched.
patching your web.xml
+If your blocks contain /META-INF/cocoon/xpatch/*.xweb files, they are +applied to the /WEB-INF/web.xml of the resulting web archive.

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/1361_1_1.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml Added: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml URL: http://svn.apache.org/viewvc/cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml?rev=1346801&view=auto ============================================================================== --- cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml (added) +++ cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml Wed Jun 6 09:43:41 2012 @@ -0,0 +1,39 @@ +Cocoon Maven 2 Plugin - IntroductionApache Cocoon Documentation Team +

Introduction

The Cocoon Maven 2 plugin provides some goals that make the developer's life +easier. Currently it contains

Cocoon Block preparation goal

The purpose of the block preparation goal is making +a block runnable as web application and enabling rapid application +development. It uses the +Apache Commons JCI +library which provides a reloading classloader. As the names already promises, +it is able to watch resources (e.g. .class files) for changes. In such +a case the classloader will use the latest version of the resources in the +future.Some Java servlet containers already provide the automatic reload of loaded +servlet contexts in the case of changes but this comes with the downside that +you might loseÂ the application state and that you are not allowed to change the +signatures of classes and methods.

Cocoon Deployer goal

The Cocoon Deployer goal provides two features that +rewrite a web application in order to add functionality that comes from

reversing the classloader hierarchy
patching your web.xml

+ \ No newline at end of file Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: cocoon/subprojects/cocoon-maven-plugin/trunk/src/site/xdoc/index.xml ------------------------------------------------------------------------------ svn:mime-type = text/xml