Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325169

Summary: JSP Debugger can't find source file during remote jsp debugging on weblogic 10 mp2
Product: [WebTools] WTP ServerTools Reporter: Missing name Mising name <saadshakil>
Component: jst.serverAssignee: jst.server <jst.server-inbox>
Status: NEW --- QA Contact: Angel Vera <arvera>
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Missing name Mising name CLA 2010-09-13 17:14:59 EDT 
Build Identifier: 20100218-1602

This bug is similar to this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=104401

The difference is that the current project is a 'java project' and not a web project.

The debugger stops at the selected line but it cannot find the source, even though the path has been specified clearly under the "Edit Source Lookup Path" window. The addition of the server's stage path where the exploded war file containing the jsp file did not work.  Neither did configuring weblogic.xml's jsp-param.



Reproducible: Always

Steps to Reproduce:
1. setup java project from an existing source
2. build project separately using ant script from windows command prompt
3. start weblogic with debug start up args and deploy app separately using WLST
4. setup a couple breakpoints on the servlet that handles the jsp to see that the debugger is working with java files
5. step through until the intended line in the jsp is reached and observe the jsp source is not displayed