- This topic has 80 replies, 13 voices, and was last updated 17 years, 7 months ago by Loyal Water.
-
AuthorPosts
-
Riyad KallaMemberrvanbree, I’m not following what you are reporting… can you please clarify?
rvanbreeMemberI am having the same problem debugging jsp files – But I have some new twists
WinXP – WL8sp2 – JDK 1.4.x JEE 1.3 Library. [even tried using weblogic.jar instead of JBossEE and javax.servlet.jar]
I can and have created a new proj – added 1 jsp MyJsp.jsp – deployed to WL – debugs fine .
The file struct is JSP/html at top ( no webroot) like my existing project.
Explode my app into the same file system. – refreshed so all the files are known to the IDE.
Cannot debug any existing or new jsps- Except I can still debug MyJsp.jsp!
I create a new jsp – cannot debug – copy MyJsp.jsp to MyJsp2.jsp – cannot debug –
But I can still debug MyJsp.jsp even if I edit it.
I have searched the deployed FS and all classes and generated java servlets are there with the classes.
Riyad KallaMemberI think this may be a problem with lookup when the webroot and project root are the same. We have two bugs with validation and autocomplete in this case and I think this might be related. I’ll file a bug for the dev team to look into it.
toconnorMemberFor what is is worth, I am having the same problem using MyEclipse 5.0.1 and WebLogic 9.2. In my case I have a webroot directory. JSPs are in a subdirectory webroot/resources/jsp. I have tried everything I have found on the forums to no avail. When putting a breakpoint in a jsp, I get “source not found”. I have found one semi-nasty workaround that works for me.
Put breakpoint in jsp. Allow “source not found error” to occur. Click continue icon to get out of jsp. Then stop and start the server with the breakpoint in place and without redeploying the code. Jsp debugging then works for that jsp only. (You can add / remove breakpoints in that jsp and they work with source displayed.) You still cannot put workable breakpoints in other jsps even if they have already been compiled. It seems you have to stop and start the server with the breakpoint in place. I don’t get it………
Riyad KallaMemberFor everyone that has their WEB ROOT the same as their PROJECT ROOT and are using WebLogic, is there any way you can test your same project (maybe a new sample project with 1 JSP?) on Tomcat and then on WebLogic to see if the problem is with WebLogic? I tried this locally and my Tomcat experienced worked fine, I just installed WebLogic and will be testing it shortly to see if it’s an issue with WL.
toconnorMemberI ran a quick test using Tomcat 5.5 and did not have any problem. It worked right from the start. (As noted above, I get “source not found” when using WebLogic 9.2, unless I stop and start the server with the breakpoint in place, then I can freely debug that jsp only.) Thanks for looking into this. This is a big issue for us (as I’m sure it is for others). I sold MyEclipse to our company in part on its ability to debug WebLogic jsps which (at least at the time) Eclipse / WTP did not support..
toconnorMemberI should have mentioned. I ran the same little test project in both Tomcat and WebLogic. I had 1 jsp under the root, one under a resources/jsp folder. In either case it worked fine in Tomcat. In both cases, I got “source not found” in WebLogic 9.2, unless I stopped and restarted the server with breakpoints established……
rvanbreeMemberAs I said a simple test is not a problem. When I add my existing code ( many 100’s of jsp files ) I cannot break on any new files.
Anthony EstelitaMemberWe are have the same problem as [toconnor], exept we are using Weblogic 8.1SP5. I tried the set break point in jsp and stop and restart the server and bygoly it worked as [toconnor] stated. Too bad we have 1000s of JSP; because, i was thinking of setting breakpoints in all the files then stop the server, then after it is started i would disable them. 😀 Very painful, but it helps debugging (you can only get so much from a System.out). We look forward to this issue being resolved.
Thank you,
Anthony
Riyad KallaMemberAnthony,
Just to clarify, is your webroot also your project root?
Anthony EstelitaMemberI am not sure if I fully undertand the question. I have a WEB project that looks like the following:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
myWeb
\src
——\com
\WebRoot
——\webFiles
——\WEB-INF
———–web.xml
———–weblogic.xml
———–\lib
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~And my “myWeb” project properties are the following:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Web-root folder: /WebRoot
Web Context-root /myWeb
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
moreinforequiredMemberWhen I put a debug point in the JSP, I get the source not found error. But when I restart the server, it stops just fine.
This has now been reported by many folks. So there is definitely some issue with MyEclipse. It is not a show stopper but becomes really annoying when you have tons of JSPs.
Could someone from Support please look at this issue with Weblogic and fix it when they can.
Thanks
Riyad KallaMembermoreinforequired,
Is your WebRoot also your Project root?We have looked into this and continue to look into it, the problem is reproduction which is why it’s slow going. Also for the last 2 weeks we’ve been heads down getting 5.1 release, should ship Monday.
moreinforequiredMemberRiyad
I am not quite sure what you are asking but here are the details for my project :MyEARProject
–/lib
–/META-INF
–/META-INF/application.xmlMyEARWebProject
–/JavaSource
–/TestSource
–/WebContent
–/WebContent/WEB-INF
–/WebContent/WEB-INF/web.xml
–/WebContent/WEB-INF/weblogic.xml
–/WebContent/WEB-INF/lib
etc..My application.xml looks like this :
<application>
<display-name>MyEar</display-name>
<module id=”myeclipse.1160765383499″>
<web>
<web-uri>MYEARWeb.war</web-uri>
<context-root>/MYEARWeb</context-root>
</web>
</module>
</application>Please let me know if you need any other thing
Riyad KallaMemberThat’s great, that’s the information I wanted. Thank you.
-
AuthorPosts