cvs commit: jakarta-tapestry/src/documentation/content/xdocs index.xml

[hl...@apache.org]

hlship      2005/06/23 07:44:06

  Modified:    src/documentation/content/xdocs index.xml
  Log:
  Add some teaser details about upgrading to the project home page.
  
  Revision  Changes    Path
  1.14      +64 -1     jakarta-tapestry/src/documentation/content/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-tapestry/src/documentation/content/xdocs/index.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- index.xml	19 Jun 2005 15:00:45 -0000	1.13
  +++ index.xml	23 Jun 2005 14:44:06 -0000	1.14
  @@ -125,7 +125,8 @@
     </li>
     <li>
       Tapestry 4.0 makes much less use of reflection and &OGNL; than Tapestry 3.0; partly
  -    because there are many new <link href="UsersGuide/bindings.html">binding prefixes</link>.
  +    because there are many new <link href="UsersGuide/bindings.html">binding prefixes</link> and largely
  +    because of how parameters are now implemented.
     </li>
     <li>
      HiveMind services and &Spring; beans to be directly injected
  @@ -155,6 +156,10 @@
     <li>
       Page properties can now be persisted on the client, as well as in the session.
     </li>
  +  <li>
  +    Components and component parameters can now be marked as deprecated. Component parameters may
  +    have aliases (used when renaming a parameter).
  +  </li>
   </ul>
   
   <p>
  @@ -180,6 +185,64 @@
   momement, it is still recommended that you stick with Tapestry <strong>3.0.3</strong>,
   the latest stable release.
   </p>
  +
  +<warning>
  +One new feature of Tapestry 4.0, default bindings for parameters, has proven to be quite controversial.
  +This feature allows you to define a default binding prefix for a parameter as part of the &lt;parameter&gt; 
  +element.  Then in your template, you can omit the prefix ... this allows you to say
  +<code>value="userId"</code> rather than <code>value="ognl:userId"</code>,
  +or <code>listener="doSubmit"</code> rather than <code>value="listener:doSubmit"</code>.
  +The pros and cons are still being evaluated and exposure of the beta release may provoke a new discussion
  +and possibly the removal of this feature. If you are intending to start work on a production application
  +using Tapestry 4.0, you are advised to <em>always</em> use an explicit binding prefix.
  +</warning>
  +  
  +</section>
  +
  +<section>
  +  <title>Upgrading from Tapestry 3.0</title>
  +  
  +  
  +<p>
  +  Tapestry 4.0 features a large number of new features, and is some limited cases, backwards compatibility
  +  has been compromised.  <link href="site:upgrade">Full details</link> are forthcoming, but in general:
  +</p>  
  +
  +<ul>
  +  <li>Tapestry 3.0 page and component specifications are still honored</li>
  +  <li>Page and component templates have not changed</li>
  +</ul>
  +
  +<p>
  +Things that will cause you trouble when upgrading:
  +</p>
  +
  +<ul>
  +  <li>Defining engine services has changed entirely, as has the IEngineService API</li>
  +  <li>Subclassing BaseEngine to override exception handling has changed; it is now about
  +    creating and contributing new HiveMind services to override the default behavior.</li>
  +  <li>
  +    Parameter direction "custom" is no longer really supported. Defining a parameter
  +    always creates a corresponding property.
  +  </li>
  +  <li>
  +    The <em>parameterName</em>Binding property is no longer created for each parameter,
  +    instead you must use the getBinding() method.
  +  </li> 
  +   <li>
  +    The relationship between the page loader and the specification delegate has changed;
  +    the specifications provided by the delegate are now cached by the loader (in 3.0,
  +    the delegate was responsible for caching).
  +   </li>
  +   <li>The Jakarta commons-lang library is no longer a dependency of Tapestry; this means
  +    that the EnumPropertySelectionModel class is no longer available (however, you can easily
  +    copy the source from Tapestry 3.0). </li>
  +</ul>
  +
  +<note>
  +We apologize for any lack of documentation; the alpha period for Tapestry 4.0 has been marked by furious
  +activity, the beta period is about bug fixing and catching up on the documentation.
  +</note>
     
   </section>
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org