Documentation Patch for upgrade.xml

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Documentation Patch for upgrade.xml

richard.hensley
Here is a patch that updates the upgrade documentation about some guidance
on migrating services. I was unable to load forrest and build the
documentation to take a peek, so it requires review.

Index: upgrade.xml
===================================================================
RCS file:
/home/cvspublic/jakarta-tapestry/src/documentation/content/xdocs/UsersGuide/
upgrade.xml,v
retrieving revision 1.9
diff -u -r1.9 upgrade.xml
--- upgrade.xml 6 May 2005 17:29:10 -0000 1.9
+++ upgrade.xml 12 May 2005 18:12:31 -0000
@@ -49,6 +49,25 @@
   
 <p>
 Engine services are now defined using HiveMind, in the
<code>tapestry.services.ApplicationServices</code> configuration point.
+The following is the chart service from the Workbench example.
+</p>
+
+<p>
+<code>
+  &lt;contribution
configuration-id="tapestry.services.ApplicationServices"&gt;
+    &lt;service name="chart" object="service:Chart"/&gt;
+  &lt;/contribution&gt;
+  
+  &lt;service-point id="Chart"
interface="org.apache.tapestry.engine.IEngineService"&gt;
+    &lt;invoke-factory&gt;
+      &lt;construct class="chart.ChartService"&gt;
+        &lt;set-object property="exceptionReporter"
value="infrastructure:requestExceptionReporter"/&gt;
+        &lt;set-object property="response"
value="infrastructure:response"/&gt;
+        &lt;set-object property="linkFactory"
value="infrastructure:linkFactory"/&gt;
+      &lt;/construct&gt;
+    &lt;/invoke-factory&gt;
+  &lt;/service-point&gt;
+</code>
 </p>
 
 <p>
@@ -57,7 +76,16 @@
 
 <p>
 The &IEngineService; interface has changed in non-backwards compatible
ways. If your application created
-custom engine services, you will have to make changes to your code.
+custom engine services, you will have to make changes to your code. If your
custom service was
+based on the <code>org.apache.tapestry.engine.AbstractService class<code>,
that class has been removed
+so you will have significant rewrites. As a suggested course of action,
find the service
+that the original service was based on, and build a new service based on
that Tapestry service.
+For example, if the original service was based on
<code>org.apache.tapestry.asset.AssetService<code>, then
+get the source for the AssetService, and model your service after the new
implementation.
+</p>
+
+<p>
+
 </p>
 
 </section>  <!-- upgrade.service -->


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]