0

Platform I am using:

  • Fedora 20;
  • mariadb-5.5.34-2.fc20.x86_64;
  • Eclipse Kepler Service Release from www.eclipse.org

I am implementing example

See here

and I am trying to manage to work the login interface. Actually I am configuring TomEE to use JAAS auth technology. Since I am having some troubles, I would like to solve them with the help of Eclipse debugging mode. To do that, I:

  • setted breakpoint at line number 79 of LoginController.java;
  • started TomEE in debug mode;
  • executed login.xhtml in debug mode too;

My problem is that I see nothing in debug mode: no variables, etc. How is it possible? I have been using debugging mode for a long time, but it is my first time in web development. Project archive

Click here for a larger Screenshot enter image description here

MWiesner
  • 8,868
  • 11
  • 36
  • 70
Germano Massullo
  • 2,572
  • 11
  • 40
  • 55
  • 2
    I am not sure the debugger has stopped at all in that picture. Could you show us another picture putting the breakpoint at line 81? – Jorge_B Jan 02 '14 at 17:58
  • @Jorge_B ONE http://imageshack.com/a/img191/9279/q54j.png TWO http://imageshack.com/a/img23/5489/9lp5.png – Germano Massullo Jan 02 '14 at 20:49
  • If the debugger would have stopped in a breakpoint, you would find that in the "Debug" window one of the daemon threads would have spanned into a call stack trace, just like when you call `.printStackTrace()` on a java exception. Could you show me an image of that? By clicking on the top of the call stack, you should see the variables in the "Variables" window – Jorge_B Jan 02 '14 at 20:55
  • By the way, there is an easier explanation for all this, now I think of it: have you started your Tomcat in debug mode? You can check it in the "Servers" window under Java EE perspective – Jorge_B Jan 02 '14 at 20:56
  • Yes I started Tomcat in debug mode. I do not know how to do what you asked me in '.printStackTrace()' What about the terminated process you can see in http://imageshack.com/a/img543/9859/pz6f.png – Germano Massullo Jan 02 '14 at 21:24
  • No, I just meant that, in case that the server stopped in debug mode, you would see in that window the full call trace in the fashion that method paints it. I don't know what your problem can be, it must be some detail that flees you. Maybe the class you have put the breakpoint in has been recompiled since you deployed it and the debugger can't find the exact line number because they have changed? – Jorge_B Jan 02 '14 at 21:28
  • I did not change the class I putted the breakpoint in. Can a recorded video be better than screenshots? If yes I can record one – Germano Massullo Jan 02 '14 at 21:30
  • let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/44357/discussion-between-jorge-b-and-caterpillar) – Jorge_B Jan 02 '14 at 21:37

1 Answers1

0

The webpage bean has not been istantiated for an unknown reason. I opened a new question to fix it. Bean not instantiated

Community
  • 1
  • 1
Germano Massullo
  • 2,572
  • 11
  • 40
  • 55