A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1297.html
Document ID: 1297
Branch: main
Language: default
Name: Using the Reloading Classloader (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 3/3/07 9:57:49 AM
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: 4272 bytes (previous version: 4258 bytes)
Content diff:
(8 equal lines skipped)
<p>If you don't know what the reloading classloader plugin is for, see the
<a href="daisy:1295">introduction</a> of the plugin documentation.</p>
+++ <p>These instructions should work with any Cocoon block. Cocoon web
applications
+++ aren't supported yet. The sample configurations are based on the
+++ <a href="daisy:1159">Getting Started guide</a>.</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 <tt>rcl.properties</tt> in the root directory of your block
with
--- a content like this:</p>
+++ properties file <tt>rcl.properties</tt> in the root directory of the block
that
+++ you want to run with a content like this:</p>
<pre><strong>com.mycompany.myBlock1.block%classes-dir</strong>=./target/classes</pre>
(35 equal lines skipped)
<h1>Step 4: Create Eclipse project files</h1>
--- <p>Move to getting-started-app/ and invoke</p>
+++ <p>Move to <tt>getting-started-app/ </tt>and invoke</p>
<pre>mvn eclipse:eclipse</pre>
<p>and import the new Eclipse project into your Eclipse workspace.</p>
<h1>Step 5: Start the servlet container</h1>
--- <p>Now you can configure the Maven 2 Jetty plugin to use this web
application:
--- </p>
+++ <p>Now you can configure the Maven 2 Jetty plugin to use the web application
+++ that was created by the block in <tt>target/rcl/webapp</tt>:</p>
<pre><project>
<build>
(29 equal lines skipped)
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>
--- <p>Call <tt>http://localhost:8888/block1/</tt> in your browser!</p>
+++ <p>Call mvn <tt>jetty:run</tt> and point your browser to
+++ <tt>http://localhost:8888/block1/</tt> in your browser.</p>
<h1>Alternative step 5: Use Jetty in 'debug mode' within Eclipse</h1>
(4 equal lines skipped)
<p>Now it's time to see the reloading classloader in action. Open
<tt>getting-started-app/myBlock1/src/main/java/com/mycompany/???</tt> and
change
--- it, e.g. ...<br/>
--- At the Jetty console you should see a notification that a file has changed.
--- Refresh your browser and you should see the changed values there.</p>
+++ it. Refresh your browser and you should see the changed values there.</p>
--- <p class="note">The Spring application context isn't refreshed. This means
that
--- changes to Spring appliation context configurations and beans of the scope
--- <tt>prototype</tt> still need a reload of the web application context.</p>
---
</body>
</html>
