Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by ErikVullings: http://wiki.apache.org/tapestry/BoardReportApril2007 ------------------------------------------------------------------------------ - Tapestry development is continuing in the 4.1 and 5 branches. + == Tapestry 4.1.2 == + Development of the 4.1.X series continues with what are more or less largely feature improvements / bug fixes / elimination of "quirks". This release is currently only waiting for the new OGNL features to stabilize - which we hope happens soon. (maybe 2-3 more weeks if you are feeling optimistic) - == Organization == + === OGNL 2.7 === + One of the feature improvements involved improving the runtime performance of a critical library used to resolve java object property expressions. - The board has alerted the Tapestry PMC of irregularities in the voting and release of the early Tapestry 4 and Tapestry 5 releases. The clarifications has been embraced, with a mix of procedural and technical changes (such that we may "vote on the binaries"). We should see the first such proper vote coming soon, for Tapestry 5.0.4. + Most of the details can be found in either links [http://blog.opencomponentry.com/2007/03/05/tentative-ognl-27-snapshot-release-out-to-blow-up-a-project-near-you/ OGNL 2.7-SNAPSHOT released], [http://blog.opencomponentry.com/2007/01/14/new-ognl-release-on-the-horizon-its-faster/ new ognl release coming..]. The gist of it is that a new bytecode compilation step has been added to the process to translate the ast generated object graph from typical ognl expressions into their pure(er) java bytecode form - making for a much faster runtime. - The Tapestry PMC is also looking to extend the size of the Tapestry committer community. Several active users meet the qualifications and a vote is expected soon. + It is expected that these changes will also eventually make their way into [http://struts.apache.org/2.0.6/ Struts 2]. Specifically - Patrick Lightbody from opensymphony / Jesse have been collaborating on bringing the project forward and outlining features that more projects need with newer jvm's. (such as [http://opensymphony.com/xwork XWork] / webwork / struts2 / etc...) There is even speculation that should the 1.5 java.lang.Type support come in Tapestry 5 may think about using them. - == Tapestry 4.1 == - - Development of the 4.1.X series continues with feature improvements, bug fixes and the elimination of "quirks". In addition, Jesse Kuhnert has taken a leadership role in the development of the OGNL library on which Tapestry depends, and has been implementing an OGNL-to-bytecode compiler that will result in about a 30x - improvement of performance of OGNL expressions (which account for at least 50% of the time spent processing a Tapestry request). It is expected that new OGNL library, release 2.7, will be nailed down within a few more weeks. - - The OGNL changes will be useful well outside the domain of Tapestry; Jesse has been in active communication with Patric Lightbody on furthering OGNL, potentially for use with WebWork, Struts 2 and elsewhere. - - == Tapestry 5 == - - Tapestry 5 continue to steam forward, adding new features and documentation. A bit of effort has been expended over the last few weeks to simplify the IoC container, adapting ideas from Google's Guice. Other simplifications are targetting to streamline integration with Spring, an important feature for the majority of users. - - User contributed patches have simplified and improved deployment of Tapestry application into a number of application servers (ironing out tricky class loading issues that are application-server specific). - - Beyond Apache, outside users are already creating reusable Tapestry 5 component libraries, a very encouraging development. - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
