You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Alan Chandler <al...@chandlerfamily.org.uk> on 2005/09/11 13:55:31 UTC
Debugging Abstract Classes
IS there a way to find and then put a breakpoint on the abstract classes
created by Tapestry?
--
Alan Chandler
http://www.chandlerfamily.org.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: Debugging Abstract Classes
Posted by Patrick Casey <pa...@adelphia.net>.
You can make concrete properties instead of abstract ones which
makes the debugging easier. It's what I usually do.
e.g. instead of:
public abstract PersonSummary getThisChild();
do
private PersonSummary fThisChild;
public setThisChild(p PersonSummary) {
fThisChild = p;
}
Public PersonSummary getThisChild() {
Return fThisChild;
}
> -----Original Message-----
> From: Alan Chandler [mailto:alan@chandlerfamily.org.uk]
> Sent: Monday, September 12, 2005 10:38 AM
> To: tapestry-user@jakarta.apache.org
> Subject: Re: Debugging Abstract Classes
>
> On Sunday 11 September 2005 17:41, Geoff Longman wrote:
> > You can put breakpoints in your abstract class as per normal and it
> > should work. You can't debug into the code added by Tapestry at
> > enhancement time as there is no source code generated by the
> > enhancement process.
> >
> > (YMMV - I'm an eclipse user so my experience debugging Tapestry apps
> > is, of course, Eclipse related).
>
> I'm using Eclipse too - on linux.
>
> I was looking to check what exactly was happening in some cases - and
> since I
> have been avoiding using component specifications, I have a number of
> classes
> that are purely abstract.
>
> I know I can put breakpoints on actual code (and I have), but I have a
> number
> of classes of the form supporting a @Foreach component inside the html
> template. It would be nice to get to see the values of my
> "PersonSummary" (or equivalent for other components) at each iteration
> round
> the loop"
>
> @ComponentClass
> public abstract class Children extends BaseComponent {
>
> @Parameter
> public abstract List<PersonSummary> getChildList();
>
> public abstract void setThisChild(PersonSummary thisChild);
> public abstract PersonSummary getThisChild();
>
> }
>
>
> --
> Alan Chandler
> http://www.chandlerfamily.org.uk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Debugging Abstract Classes
Posted by Alan Chandler <al...@chandlerfamily.org.uk>.
On Sunday 11 September 2005 17:41, Geoff Longman wrote:
> You can put breakpoints in your abstract class as per normal and it
> should work. You can't debug into the code added by Tapestry at
> enhancement time as there is no source code generated by the
> enhancement process.
>
> (YMMV - I'm an eclipse user so my experience debugging Tapestry apps
> is, of course, Eclipse related).
I'm using Eclipse too - on linux.
I was looking to check what exactly was happening in some cases - and since I
have been avoiding using component specifications, I have a number of classes
that are purely abstract.
I know I can put breakpoints on actual code (and I have), but I have a number
of classes of the form supporting a @Foreach component inside the html
template. It would be nice to get to see the values of my
"PersonSummary" (or equivalent for other components) at each iteration round
the loop"
@ComponentClass
public abstract class Children extends BaseComponent {
@Parameter
public abstract List<PersonSummary> getChildList();
public abstract void setThisChild(PersonSummary thisChild);
public abstract PersonSummary getThisChild();
}
--
Alan Chandler
http://www.chandlerfamily.org.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Debugging Abstract Classes
Posted by Geoff Longman <gl...@gmail.com>.
You can put breakpoints in your abstract class as per normal and it
should work. You can't debug into the code added by Tapestry at
enhancement time as there is no source code generated by the
enhancement process.
(YMMV - I'm an eclipse user so my experience debugging Tapestry apps
is, of course, Eclipse related).
Geoff
On 9/11/05, Alan Chandler <al...@chandlerfamily.org.uk> wrote:
> IS there a way to find and then put a breakpoint on the abstract classes
> created by Tapestry?
> --
> Alan Chandler
> http://www.chandlerfamily.org.uk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org