Yes, if you create concrete implementation of all your properties, you do not get an enhanced classed. However, you must follow the initialize() rules, and persistent property rules, which I don't remember off the top of my head because I let Tapestry handle it with Class Enhancement.
Richard -----Original Message----- From: Patrick Casey [mailto:[EMAIL PROTECTED] Sent: Monday, May 02, 2005 9:36 AM To: 'Tapestry users'; 'Michael Musson' Subject: RE: Tapestry Enhanced Classes I could be wrong on this, but if you create properties for your page class, then tapestry won't have to enhance it, will it? I've never been personally comfortable with "fing magic" techniques (like automatic class enhancement, etc) so I've been using concrete setters and getters in my page classes from the get-go and don't recall any of the classes being flagged as enhanced in the debugger. --- Pat -----Original Message----- From: Michael Musson [mailto:[EMAIL PROTECTED] Sent: Monday, May 02, 2005 8:31 AM To: Tapestry users Subject: Tapestry Enhanced Classes I have a .page file that defines a property. Tapestry enhances my page class by adding a member and the getter/setters and some reset/seriallize on change functionality. This enhancement creates a new class with the auto-generated code. The generated class is causing all sorts of difficulties with the debugger. Is there any way to pregenerate this class before deploying to the server? Or at the very least, enhance the class in a way that doesn't make the debugger confused? --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
