Classes that will be transformed must be segregated by package, otherwise the class loader will attempt to transform non-components, such as JDK classes and such. Tapestry is under some constraints to do the transformation at runtime (so as not to complicate the build/deploy process) and to do it incrementally (so as to not affect application start up time for very large applications).
On 5/28/07, Jun Tsai <[EMAIL PROTECTED]> wrote:
2007/5/28, Howard Lewis Ship <[EMAIL PROTECTED]>: > > Very good. > > Also in terms of the choice of Javassist methods: super-class event > handler > methods are recognized when the super-class itself is enhanced. That's > why > there's a "com.foo.example.app.base" package ... for base classes to pages > and components. I think 'com.foo.example.app.base" base classes package is not a good idea,because some base page classes not in the base package.why not instruments the parent class directly? -- > Howard M. Lewis Ship > TWD Consulting, Inc. > Independent J2EE / Open-Source Java Consultant > Creator and PMC Chair, Apache Tapestry > Creator, Apache HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > -- Welcome to China Java Users Group(CNJUG). http://cnjug.dev.java.net
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
