Thanks for the info- but this isn't exactly what I am asking.  First of all,
I am a MyFaces USER not a developer.  I use Eclipse and JBoss and I know how
to do debugging of my code.  My issue is basically the stack trace I have
included.  None of the classes in the stack trace are mine.  They are all
Myfaces / Trinidad or utility.

So my responsibility as a Faces developer is to correctly assemble a
component tree and then let the Faces implementation either render the tree
I have built OR tell me what I'm doing wrong.  The state of MyFaces is such
that it does not catch everything that I am doing wrong and instead results
in a stack trace as I have included.  My real concern is HOW do I figure out
what I have done wrong short of looking at Apache source code.

I am wondering what other people do when faced with this problem.  As for
me, I generally start removing things and adding them back in until I
localize the problem area, then try different things until it starts
working.

On Fri, Feb 15, 2008 at 12:12 PM, Curtiss Howard <[EMAIL PROTECTED]>
wrote:

> I generally use Eclipse's remote debugging facilities.  I'm not sure
> what appserver you're using, but with Tomcat you can do the following:
>
> set JPDA_ADDRESS=8000
> set JPDA_TRANSPORT=dt_socket
> catalina jpda start
>
> Then in Eclipse you select a project, choose "Open Debug Dialog" and
> create a new "Remote Java Application" configuration.  The default
> values will connect to the Tomcat server you just started.
>
> You should have all the appropriate Myfaces source trees imported as
> projects.  Then, just set breakpoints in the code and hit your
> application as normal.  It will suspend whenever one of the breakpoints
> is hit.  Then you can do the normal debugger stuff: continue execution,
> step over, step into, etc.  Eclipse will also list all the variables in
> use and their values.
>



-- 
"Many men go fishing all of their lives without knowing it is not fish they
are after."

- Henry David Thoreau

Reply via email to