Hints on debugging

[gommo]

I've just started out with Seam. I'm doing a simple login box and have borrowed most of the ideas from the booking example.

However, when I click on my login button the browser's wait cursor starts but nothing happens. Eventually I get a timeout network connection error box (I'm using Icefaces as well, I think that is what issues the timeout box).

I can't see any errors in Jboss.

What debugging steps can I go down to hunt this down. I'm using the Identity object similar to the booking example. I've ensured I have my authenticator pointing to the method I want to use to authenticate the user etc..

I'm a little stumped

Thanks

[kruno]

You can edit jboss-4.2.0.GA/server/default/conf/jboss-log4j.xml if you are using jboss 4.2 or jboss-4.0.5.GA/server/default/conf/log4j.xml

and change :

<root>
 <level value="DEBUG"/>
 <appender-ref ref="CONSOLE"/>
 <appender-ref ref="FILE"/>
 </root>

but that is a lot of debug.
cool thing is that you do not have to stop server to change logging level

[moshe1]

On the icefaces side, use firefox + firebug. You can see what is being sent to the server, and the response (which can be stack traces which don't always show up in the standard logs)

Attach a debugger to jboss and put breakpoints in your authentication method.
If all else fails you can always download the source for seam and put breakpoints in the seam src.

[monkeyden]

Is the application deployed in the context root? We had a similar issue, which forced us to scrap ICEFaces.

http://jira.icefaces.org/browse/ICE-1579