- This topic has 6 replies, 2 voices, and was last updated 20 years, 2 months ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version: WINXP Pro, SP1
Eclipse version: Version: Version: 3.0.0
Eclipse build id: Build id: 200406251208
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 7
MyEclipse version: 3.8.1
Eclipse JDK version: SUN 1.4.2_03-b02
Application Server JDK version: SUN 1.4.2_03-b02
Are there any exceptions in the Eclipse log file? No– Message Body ——————————-
I can only set a debug break on a line of java script inside a JSP.Previously, with myEclipse 2.7 I was able to set a break point inside a Custom Tag.
Is this JSP break point functionality a limitation of Eclipse 3.0 or myEclipse 3.8; or is it a bug?
We actually followed a design decision of WSAD’s in that we only allow breakpoints at Java code in JSP pages now, if you wish to debug a custom tag, you can set the breakpoint in the tag class.
Please let us know if this is not suitable for your development.
Actually I found the previous implementation more useful.
I realize I can set a breakpoint in the java file for the custom tag, but in most cases the tag files are open source JSTL tags. Sometimes I have the source jars available, other times I don’t. Even with the JSTL source available, I’m not familiar with the actual code implementation.
Furthermore, it is our development team’s best practice to not use java scriplet code inside a JSP; which essentially disables JSP debuging in Eclipse 3.0
The abilitiy to set a break point anywhere in the JSP was a highly useful feature (and one that will be missed).
It allowed for inspection of HTTP request/session parameters just prior to JSP elaboration, allowed for validating conditional JSP logic and was another tool available to the developer for troubleshooting JSP specific issues.I would like to see this functionality return in a future release of myEclipse.
I will certainly send your comments to the team as we don’t want to hinder anyone’s development and see if it would be easy enough to put this back in (I am not privy to the impl details, it might be a bear to do).
sjones,
The team liked your arguments and we are tenatively going to try and nail it for the 3.8.2 release. Thank you for taking the time to let us know what you think.It’s a unique experience to actually have some influence on the features available in MyEclispe.
Thanks for all the support and taking the time to listen to your User Community.
The only thing we ever regret is that we can’t implement some of the requested features overnight, so a user may feel “forgotten” if their request isn’t in the next release, but then surprised when its in the release after that 😉
The balancing of what to do and what to not do is extremely difficult to give the biggest benefit to most people… luckily our management is a group of brilliant guys.
