You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by da...@cocoon.zones.apache.org on 2006/12/27 20:21:29 UTC
[DAISY] Updated: Usage
A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1297.html
Document ID: 1297
Branch: main
Language: default
Name: Usage (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 12/27/06 7:21:13 PM
Updated by: Reinhard Pötz
A new version has been created, state: publish
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 1465 bytes (previous version: 37 bytes)
Content diff:
--- <html><body><p>TODO</p></body></html>
+++ <html>
+++ <body>
+++
+++ <p class="note">Note: The Spring application context isn't refreshed. This means
+++ that changes to Spring appliation context configurations and beans of the scope
+++ "prototype" still need a reload of the web application context.</p>
+++
+++ <h1>Step 1: Provide the configuration</h1>
+++
+++ <p>If you want to use the reloading classloader plugin, you have to provide a
+++ properties file like this:</p>
+++
+++ <pre>...</pre>
+++
+++ <p>The property names consist of the block name (more exactly, the name of the
+++ Spring bean that represents a block) + <tt>%CLASSES_DIR</tt> (e.g.
+++ <tt>org.mycompany.myBlock.block%CLASSES_DIR</tt>). The value is the relative or
+++ absolute filesystem path.</p>
+++
+++ <h1>Step 2: Enable the plugin in pom.xml</h1>
+++
+++ <p>In the pom.xml you have to add the plugin:</p>
+++
+++ <pre>...
+++ </pre>
+++
+++ <h1>Step 3: Invoke the plugin</h1>
+++
+++ <p>The Maven 2 plugin can be invoked by calling</p>
+++
+++ <pre>mvn cocoon-rcl:webapp
+++ </pre>
+++
+++ <p>This creates a web application into ./target/rcl/webapp for your block.</p>
+++
+++ <h1>Step 4: Start the servlet container</h1>
+++
+++ <p>Now you can configure the Maven 2 Jetty plugin to use this web application:
+++ </p>
+++
+++ <pre>...
+++ </pre>
+++
+++ <p class="note">Unfortunatly, under certain (still unknown) circumstances there
+++ seems to be a problem with the reloading classloader which can only be worked
+++ around by starting your JVM in debug mode from within your IDE.</p>
+++
+++ <h1>Alternative step 4: Use Jetty in 'debug mode' within Eclipse</h1>
+++
+++ <p>TODO</p>
+++
+++ </body>
+++ </html>