Ther'es a debugging option, -Djavassist-write-dir=target/javassist
With that enable, Tapestry will write out the bytecode for any classes it creates or transforms. I then used the Jad decompiler to "view the source". Alternately, you can see the transformations for a particular component class by enabling debug logging for that class (i.e., in log4j properties). That shows you the Javassist code from which the bytecode is generated. Or you could trust in the force, it is strong in this one :-) On 3/2/07, 黄翔 <[EMAIL PROTECTED]> wrote:
I think the code generated for components is really useful for debugging and understanding. So , is there some way I can view the source code. -- huang xiang Guangzhou, China.
-- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
