Well, you don't find bugs in the enhanced code, the bugs (runtime exceptions) point back to your own code. After a while of working like this, and knowing your own app, you begin to understand where the bugs originate by e.g. looking at the stack trace and thinking about how things should be working by keeping in mind the architecture of the app. There is also a clear distinction between what is set up as components and in the module descriptor and what you add in your own code. That is there are typical bugs associated with the former and once that is stable it is possible to work on elaborating your code to take account of, say, business logic or display requirements only touching your .jwc in a very controlled way, so you would have a very good idea where the bugs originate at this stage.
Adam > -----Original Message----- > From: Vadim Pesochinskiy [mailto:[EMAIL PROTECTED] > Sent: Friday, July 01, 2005 5:19 AM > To: Tapestry users > Subject: Re: Anyone looked at BetterPetShop? > > Yes, that helps. Thanks a lot. > > Bright idea, it would be interesting to try find bugs in code that does > not exist. I am wondering how far run-time byte code generation will go... > > Todd O'Bryan wrote: > > > Because if you implement the methods, you're responsible for > > initializing and otherwise dealing with the page properties. If you > > leave them abstract Tapestry takes care of all of that for you. You > > only have to even declare the abstract methods if you actually call > > them in your own Java code, and that's just to make the compiler > > happy. Any calls that Tapestry makes internally (to set or get > > properties from the page) happen automatically. > > > > It's a little confusing and indirect, but it really does make your > > life easier. > > > > HTH, > > Todd > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
