I have had eclipse do the same thing. It complains, but it stops there anyway. Had the same issue with Jetty. Put the breakpoint where you want it and then tell it to go. For me, it stopped where it was supposed to stop.
HTH, Mark -----Original Message----- From: Michael Musson [mailto:[EMAIL PROTECTED] Sent: Mon 5/2/2005 10:25 AM To: Hensley, Richard Cc: Tapestry users Subject: Re: Tapestry Enhanced Classes I am running within WebSphere 5.1. The debugger complains that the enhanced class does not contain line numbers so any break points in enhanced classes fail. Mike On 5/2/05, Hensley, Richard <[EMAIL PROTECTED]> wrote: > Michael, > > In what way is the debugger confused? We use the debugger in eclipse all the > time to debug Tapestry page classes. > > Richard > > -----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]
