And, as I said, it works fine for me. As I write this, my eclipse is
paused on the renderComponent method of the @Any component, right on the
breakpoint I put there.
--- Pat
> -----Original Message-----
> From: Dan Adams [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 10, 2005 10:49 AM
> To: Tapestry users
> Subject: RE: [OT] Debugging components in eclipse
>
> Like I said, that works fine when I write the code but if you try to set
> a breakpoint in one of the **TAPESTRY** components it doesn't work even
> if you have the src jar attached.
>
> On Thu, 2005-11-10 at 09:53 -0800, Patrick Casey wrote:
> > What version of eclipse and Tapestry are you on? I have had zero
> > problems debugging into enhanced classes via eclipse 3.1 and Tapestry
> 3.0.3;
> > class enhancement is pretty common these days (it's how Hibernate works
> for
> > example), so if there was an intrinsic debugging problem with Eclipse
> and
> > enhanced classes I'm pretty sure it would have come up by now.
> >
> > In other words, I suspect either:
> >
> > A) Your method isn't really the method that's being run.
> > B) You've got something configured wrong.
> >
> > As I said before, if you make a concret property:
> >
> > Private String fFoo
> >
> > With concrete getters and setters:
> >
> > Public String getFoo() {
> > Return fFoo;
> > }
> >
> > Public void setFoo(String s) {
> > fFoo = s;
> > }
> >
> > And define foo as a property in you .jwc e.g.
> >
> > <parameter name="foo" required="no" type="java.lang.String"
> direction="in"
> > />
> >
> > Then you can break within your setters and getters just fine.
> > --- Pat
> >
>
>
>
> ---------------------------------------------------------------------
> 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]
