- This topic has 80 replies, 13 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
I have the same problem ( posted on another thread some weeks ago ). I have upgraded again (5.1 + 3.2.X) and still have the same problem. I can debug new projects and have tried all kinds of ways to load existing jsp files – no luck, the bouble break is fixed however.
rvanbree,
Is your webroot also your project root? We did a lot of testing to make sure that scenario was working internally… I have not been able to track down what the difference between the broken projects and working projects are on the same app server, same versions and so on. All we’ve guessed at is the size/complexity of the project which has opened all sorts of doors for testing on our end that is troublesome. I’m sorry for the delay in reproducing this. If anyone has any pointers on how to break it I’d try that ASAP.Same as before – webroot = /
for sure the problem seems to be related to the number of jsp files in the project. I tried project with webroot = / and webroot = /webroot – both worked — see my previous posts – as soon as I import all the jsp files it breaks. I can debeg the files I created before the import but all others (even exact copies of the debugabble jsp ) get source not found.
Rudy
How many JSPs are we talking? I tried with 100 in the root of the project and didn’t end up with a problem… but maybe I need more?
my project has over 1500 .jsp files and over 3000 .java files – with directory/class depth 6 levels not uncommon.
Ok, I do have a project handy that is similar in size, I do need to restructure it to be in this form, but I’ll see what I can do.
I and all other developers in my group have the same problem as [anthonyestelita]. We could debug our JSPs prior to upgrading to version 5.0 of MyEclipse. We also are using Weblogic 8.1SP5. It would be a big help to us as well when this is resolved.
Thanks!
ScottScott,
Are you guys all using big projects as well or can you reproduce the problem with a smaller sized project?I’m also curious if any of you guys can redeploy your projects to WL 9.2 and see if exactly the same project continues to have problems? I’m starting to wonder if this is an app server bug….
We do have big projects, but I was able to recreate this issue using a small project that I emailed to myEclipse support. We never had any problems prior to going to 5.0, but once we upgraded myEclipse (we were using Weblogic 8.1SP5 prior to 5.0 as well) we could no longer debug our JSPs. Being able to debug our JSP files is very important and helpful for developer productivity (going back to using System.outs for debugging is archaic and slooooooow).
I know I have mentioned this before, but if there is anything we can do to help get this issue resolved please let me know (i.e. send us a jar/class file that can create a useful log file for your developers). I’ve already emailed a small project that had the problem, and that didn’t work, so maybe since we can easily produce it, then let us help you. 🙂 PLEASE. I really don’t want to go back to 4.x ;-(
We do have big projects, but I was able to recreate this issue using a small project that I emailed to myEclipse support. We never had any problems prior to going to 5.0, but once we upgraded myEclipse (we were using Weblogic 8.1SP5 prior to 5.0 as well) we could no longer debug our JSPs. Being able to debug our JSP files is very important and helpful for developer productivity (going back to using System.outs for debugging is archaic and slooooooow).
That’s right I remember, I got your project (you even sent your workspace I believe?) and we tested with that to no avail, but we did successfully use that project to uncover some other bugs that got fixed in 5.1 which was good.
I know I have mentioned this before, but if there is anything we can do to help get this issue resolved please let me know (i.e. send us a jar/class file that can create a useful log file for your developers). I’ve already emailed a small project that had the problem, and that didn’t work, so maybe since we can easily produce it, then let us help you. 🙂 PLEASE. I really don’t want to go back to 4.x ;-(
I am curious if you guys can download WebLogic 9.2 and redpeloy your proejct to it and see if all the sudden it works. If it does, then that atleast narrows our search down to the app server and/or app server connector. If it still breaks, then that puts us back on the debugger side of things.
Unfortunately we can’t use WebLogic 9.2 at this time (we use a custom Security Realm that requires 8.1SP5). 🙁
Sorry,
AnthonyCan anyone else on this thread test on WL 9.2?
Just to clarify I’m not asking anyone to convert, just to check if the behavior is the same.
Anyone? This is a hot issue for us and not being able to debug our JSPs has the potential of drastically slowing down our developer’s productivity. 🙁
Can you ask your developers to send us a class/jar file that can give them a log file with helpful information in it? I am not sure what else to do at this point? If you can’t create this and we can, then please let us try to help in any way we can. Maybe this doesn’t have to do with project setup, i sent you a project that we see the issue in but you were not able to recreate the issue with it, so maybe this issue has something to do with environment (we use a proxy server, a custom weblogic security principal, different JVM, ???). So please let us help you and others debug this issue! PLEASE!
