Tapestry 5 will use concrete classes and annotations right on the fields, not on the accessor methods. In some ways it will be more typing (i.e., if you want getters and setters you'll have to write them yourself) but the end result will be a lot less mystifying ... no abstract classes, no base classes from which to extend, no interfaces to implement (just annotations to put on fields and some methods).
On 5/2/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
A little bit off-topic, but looking at your auto-wire patch made me realize that all the Tapestry enhancement magic depends on abstract methods, which are supposedly going away in Tapestry 5. How is this kind of injection going to happen in Tapestry 5? On 5/2/06, James Carman <[EMAIL PROTECTED]> wrote: > > I'm working on some test cases right now. I'll try to update my patch in > JIRA to include them soon. >
-- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
