- This topic has 23 replies, 3 voices, and was last updated 20 years, 8 months ago by
.
-
Posts
-
I came across this in the help file:
“MyEclipse creates a work folder named .myeclipse. This directory is used as a runtime work area into which JSPs are compiled”
Is this the area used to get source code debugging to work? This directory is empty in my set-up.
Allen
AllenConquest,
Your original post was a question about what the .myeclipse folder was used for, if that wasn’t what you were asking, please clarify what it is you need help getting working. Also please answer the questions we ask for in the posting guidelines. A quick way is to hit “Post Reply” then hit the Insert button and fill out the info.The original post was asking about debugging JSP using source code (if you look at the beginning of the thread and not just this page you will see this!). Here is the system details:
– System Setup ——————————-
Operating System and version:
Eclipse version: 3M7
Eclipse build id: 200402122000
Fresh Eclipse install (y/n): Y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: JFaceDbc
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.7.1
Eclipse JDK version: 1.4.1_07
Application Server JDK version: 1.4.1_07
Are there any exceptions in the Eclipse log file?
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
!ENTRY org.eclipse.osgi Apr 13, 2004 15:33:04.484
!MESSAGE Bundle reference:file:d:/eclipse3M7/plugins/org.eclipse.debug.ui_3.0.0 [28] was not resolved
!ENTRY org.eclipse.osgi Apr 13, 2004 15:33:04.500
!MESSAGE Bundle reference:file:d:/eclipse3M7/plugins/org.eclipse.jdt.debug_3.0.0 [37] was not resolved
!ENTRY org.eclipse.debug.ui 4 120 Apr 13, 2004 15:39:04.406
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Marker id: 39181 not found.
at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:55)
at org.eclipse.core.internal.resources.Marker.getType(Marker.java:179)
at org.eclipse.debug.internal.ui.views.breakpoints.BreakpointsSorter.compare(BreakpointsSorter.java:63)
at org.eclipse.jface.viewers.TableViewer.indexForElement(TableViewer.java:337)
at org.eclipse.jface.viewers.TableViewer.add(TableViewer.java:115)
at org.eclipse.jface.viewers.TableViewer.add(TableViewer.java:134)
at org.eclipse.debug.internal.ui.views.breakpoints.BreakpointsViewEventHandler$1.run(BreakpointsViewEventHandler.java:78)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:102)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2325)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2033)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1550)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1526)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:265)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:139)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:47)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:257)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:279)
at org.eclipse.core.launcher.Main.run(Main.java:742)
at org.eclipse.core.launcher.Main.main(Main.java:581)
!ENTRY org.eclipse.core.resources 4 376 Apr 13, 2004 15:39:04.406
!MESSAGE Marker id: 39181 not found.– Message Body ——————————-
The original post was asking about debugging JSP using source code (if you look at the beginning of the thread and not just this page you will see this!)
Woops, I’m sorry I had forgotten this thread got so long.
Looking at the stack traces I’m wondering if there is something wrong with your install of Eclipse, or even something wrong with that milestone install of Eclipse (as all of the exceptions are from the debugger itself and not from our tools). Can you do a clean install/download of Eclipse 3.0M8 and MyEclipse 3.7.2 that was just released and see if that fixes the problem?
Keep in mind that the steps you *should* be able to take to get things working fine are:
-
1) Clean install of Eclipse
2) Run Eclipse, close Eeclipse
3) Clean install of MyEclipse
4) Run Eclipse, finish MyEclipse install by letting Eclipse restart itself.
5) Import your project, create new WebModule project OR checkout project from CVS as Web Module Project (of course use EJB or EAP project if it is of that type instead)
6) Setup your Tomcat 5 connector, Window > Preferences > MyEclipse > App Servers > Tomcat 5
7) Make sure to setup the connector to use a JDK to launch Tomcat with (JDK node under Tomcat 5), also make sure to “Launch” the app server in Debug mode.
8) Setup a deployment for your project, exploded or packaged.
9) Deploy project, and run App Server
10) Set breakpoint in JSP page, and execute in a browser.This is what you *should* be able to do to get debugging and what I am able to do here locally to get debugging of JSPs. Again, I appologize for the lapse of time in a response, sometimes we miss thread update notices or get swamped at a certain time and overlook some posts on accident.
I did the above with the new version and created a test web project. Guess what, the debugging started working. So I added my project configured it, and bang, it all stopped working (including the test project). After some digging around the only common thing I could come up with was the Tomcat configuration. In the perferences I had appended all our projects JAR files to the classpath to get rid of some errors that were coming up. I removed them all (leaving just classes12.jar which I needed), and amazingly the debugging started working on both the test project and my project !!!!
Success at last !!!!
However, I have one small problem with the JSP debugging. I can’t get it to stop at a breakpoint inside a struts tag. So if my JSP starts <html:html> it stops at this tag and refuses to stop at anything inbetween this and the closing </html:html> tag (including breakpoints in servlets). Is this a known problem and will it be solved. My pages are basically all struts 1.1 pages and use BEAN,HTML,JSTL, etc tags (as well as custom ones), so I need full debugging.
Thanks for everyone for sticking with me through this adventure. I just hope it might of help to someone else in the future.
Allen
Allen,
I’m glad the first part is working, I’ll ask the others about the Struts debugging, stay tuned.There’s already an outstanding issue to investigate JSP debugging inside of tags. On the surface it looks like a problem with the source map we receive from the server, but we need to dig into it and log it as a bug against Jasper 2 if that’s the case. It’s too early right now to know where the fault lies, but we’ll find out.
