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/28/06 5:08:16 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: 4069 bytes (previous version: 3516 bytes)
Content diff:
(2 equal lines skipped)
<p class="warn">The cocoon-rcl-plugin hasn't been released yet. For the time
being, you have to checkout trunk from SVN
--- (http://svn.apache.org/repos/asf/cocoon/trunk) and build it by invoking "mvn
--- install" from the root directory.</p>
+++ (<tt>http://svn.apache.org/repos/asf/cocoon/trunk</tt>) and build it by
invoking
+++ <tt>mvn install</tt> from the root directory.</p>
--- <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
--- <tt>prototype</tt> 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
(38 equal lines skipped)
<p>This creates a web application into ./target/rcl/webapp for your
block.</p>
--- <h1>Step 4: Start the servlet container</h1>
+++ <h1>Step 4: Create Eclipse project files</h1>
+++ <p>Move to getting-started-app/ 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>
(31 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/[block-name]/</tt> in your browser!</p>
+++ <p>Call <tt>http://localhost:8888/block1/</tt> in your browser!</p>
--- <h1>Alternative step 4: Use Jetty in 'debug mode' within Eclipse</h1>
+++ <h1>Alternative step 5: Use Jetty in 'debug mode' within Eclipse</h1>
<p>TODO</p>
+++ <h1>Step 6: Change a class file</h1>
+++
+++ <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>
+++
+++ <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>
