You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2004/08/27 16:05:34 UTC

[Jakarta Tapestry Wiki] Updated: Tapestry31Status

   Date: 2004-08-27T07:05:34
   Editor: HowardLewisShip <hl...@apache.org>
   Wiki: Jakarta Tapestry Wiki
   Page: Tapestry31Status
   URL: http://wiki.apache.org/jakarta-tapestry/Tapestry31Status

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -36,3 +36,13 @@
 = July 2004 =
 
 Hard at work on a Tapestry 3.0 + HiveMind application.  This has given me more insight into how to best mate the two together; much of that is reflected in recent improvements to HiveMind.
+
+= Aug 2004 =
+
+The ApplicationServlet has been gutted, replaced with a series of services, pipelines and configurations. There will be more natural places to plug in things like Hibernate transaction managers now ... the pipelines are very much like a kind of AspectOrientedProgramming, in that the pipelines provide for all kinds of extensions to the normal control flow.
+
+The test suite has grown to over 516 tests ... in a few cases, existing mock tests (really, integration tests) have been removed and replaced with clearer, more efficient, more maintainable
+unit tests.
+
+The 3.0 APIs propogated the ApplicationServlet around quite a bit.  There's now a service for accessing the ApplicationServlet, and it is represented as HttpServlet, not ApplicationServlet.
+{{{RequestContent.getServlet()}}} now returns an instance of HttpServlet.  I think, in the larger scheme of things, RequestContext is going to go away ... dissolve into a number of related services.

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