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/Tapestry31Status ------------------------------------------------------------------------------ A lot of refactoring over the last few weeks to reorganize things into proper HiveMind services. - Next up: Integrate OGNL properly (for the moment, it is kludged in). + OGNL is now represented as its own service, hidden behind an !ExpressionEvaluator interface. For now, it's still OGNL 2.x, but will be easy to upgrade to 3.x now. + Tapestry engine services are now full HiveMind services contributed into the tapestry.services.FactoryServices and tapestry.services.ApplicationServices configuration points. + The <service> element of the application specification is removed in 3.1 and ignored (with a warning) in 3.0. The !EngineServiceView interface has been removed; the functionality is now available as additional !HiveMind services that can be injected into engine service implementations. + + Refactorings are starting around component class enhancement. 3.1 will have some different behavior than 3.0. By the time I'm through, all parameters will be treated as an improved version of Tapestry 3.0's Direction.AUTO (one that properly handles non-required parameters and caches the bound expression's value). + + Changes: + * A <property> will always create a property; the checks for an existing non-abstract method have been removed. + * 3.1 will create a transient property if an abstract accessor exists for a property, even if there is no matching <property> (this falls under ''dont repeat yourself''). + * 3.1 will allow the type attribute of <property> to be ignored (more ''dont repeat yourself''). The property created will match the accessors (if they exist) or will simply be java.lang.Object (if they don't). + * 3.1 will eventually allow different kinds of persistent properties. + * 3.1 will no longer support binding properties; these were properties used to access the underlying bindings for component parameters. In 3.0, if an abstract accessor was available, Tapestry would provide and use the full implementation. + * The direction attribute of <property> will be removed in 3.1 (and ignored inside 3.0's <property-specification>). + + The upshot of this is that component properties and parameters will ''just work''. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
