• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Tim Holloway
  • Carey Brown
  • salvin francis

JSP Debug Problem in WSAD 4.0.3

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I'm experiencing JSP debugging problem in WSAD 4.0.3 (all available patched applied) running on Windows 2000. When I put a breakpoint into the JSP code, it stays with blue icon (in "regular" code in turns to green, when it's ready). Breakpoint list in Debug perspective shows all breakpoints correctly. However, the execution is never stopped at JSP breakpoint even it stops at "regular" breakpoint during the same session. Server is running in debug mode, of course. Any ideas where the problem is?
Thanks in advance...
-Alesh-
 
author & internet detective
Posts: 39435
768
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WSAD doesn't usually break at a blue icon. I don't know why but this happens in regular code too. You get a blue icon on a declaration statement like
int i=0;
Try finding something that is a "full" statement and put the breakpoint there.
 
Alesh Bukovsky
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well I noticed that WSAD doesn't break on breakpoint with blue icon. However all breakpoints in my JSP are blue and it really doesn't matter what actual code they represent.
 
Jeanne Boyarsky
author & internet detective
Posts: 39435
768
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By any chance is all of your code expressions, like:
This is the kind of thing that WSAD doesn't stop on. Try temporarily inserting a statement like:

If you put this before the code that is crashing/wrong/... at put the breakpoint on the assignment, WSAD should stop there.
 
Alesh Bukovsky
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree it should. Unfortunately it does not. I have a pile of Java code between not only . There are conditions, object constructions, method invocations etc. Regular Java code. I tried to out about 30 breakpoint at different places/instructions, no one works. I think there is something wrong with breakpoint validation mechanism. JSP debug info generation is ON as well as server debug mode. Documentation says "put a breakpoint and that's it". It doesn work for me. I do not understand at all...
 
Jeanne Boyarsky
author & internet detective
Posts: 39435
768
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree that it should stop for the code you described. It does for me.
You may have to use print statements to see variable values. At least you can modify a JSP without restarting the server.
Good luck.
 
Everybody's invited. Except this tiny ad:
professionally read, modify and write PDF files from Java
https://products.aspose.com/pdf/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!