How to Trace Seam's Navigation Logic...

[arnieoag]

I'm trying to figure out what's wrong with my .page.xml files and conversation demarcation and logic.

I can get from page 1 to 2 (no conversation) but going from 2 to 3 should start a conversation and based on a tag in page.xml, post the changes to the database.

When I press my "Add" button to get from page 2 to 3, an error occurs - but nothing is returned via my portlet (using Seam 2.1.1.GA and portlet bridge 1.0.0.CR1, facelets 1.1.14).

The log files have no real information (at least to me) that indicates what is wrong, just that its "redirecting to '/error.xhtml', which is my default error page.

Is there a package or class I can do trace logging on in order to see what's going on? I have tried logging on org.jboss.seam.navigation.*, but nothing is ever written. :(

[luxspes]

Arnie Morein wrote on May 28, 2009 21:02:


I'm trying to figure out what's wrong with my .page.xml files and conversation demarcation and logic.

Yes, that can be hard, it shouldn't, but it is

I can get from page 1 to 2 (no conversation) but going from 2 to 3 should start a conversation and based on a tag in page.xml, post the changes to the database.

Ok...

When I press my Add button to get from page 2 to 3, an error occurs - but nothing is returned via my portlet (using Seam 2.1.1.GA and portlet bridge 1.0.0.CR1, facelets 1.1.14).

Are you coding from inside eclipse? Do you see the stacktrace in the Console window? That can give a lot of clues on what is going wrong...

The log files have no real information (at least to me) that indicates what is wrong, just that its redirecting to /error.xhtml, which is my default error page.

Ok... and no stacktrace nowhere? Which one of the exceptions section in .page.xml is catching your exception?

Is there a package or class I can do trace logging on in order to see what's going on? I have tried logging on org.jboss.seam.navigation.*, but nothing is ever written.

Please vote for JBSEAM-3831. Oh and then for JBIDE-3383 too. Thanks

[arnieoag]

No stack trace, no errors, no nothing. It may be a result of the portlet bridge swallowing something.

But are you telling me there's no logging built into the Seam/Navigation code that can be traced?!?!

[yahawari]

not sure if that helps, but since u cannot see a stack trace and ur application is redirecting you to the error page, try making the error page show u what is wrong :

 <exception class="java.lang.Exception">
            <redirect view-id="/error.xhtml">
              <message severity="error">#{org.jboss.seam.handledException.message}</message>
            </redirect>
</exception>

[swd847]

if you set debug=true on core:init you should be able to display the error.