Home » Language IDEs » ServerTools (WTP) » WebTools Killed My Debugger
| WebTools Killed My Debugger [message #33377] |
Tue, 27 July 2004 19:10  |
Eclipse User |
|
|
|
Before I installed WebTools (IBM's version), I was able to have WebLogic
run internal to Eclipse by setting it up as a Java Application. I would
set the main class to "weblogic.Server", pass it the proper jvm arguments
and WebLogic would run inside of Eclipse. I could set breakpoints in any
java file being ran on the server. Now, when I run the same Debug
Application, if I set a breakpoint, it will make my webapp not respond and
it never hits the breakpoint. Somehow, WebTools is causing my debugger to
no longer perform as it once did. Has anyone seen this or have any way to
remedy? Thanks, Jeremy
|
|
|
| Re: WebTools Killed My Debugger [message #33431 is a reply to message #33377] |
Tue, 27 July 2004 19:44  |
| Eclipse User |
|
|
|
On Tue, 27 Jul 2004 23:10:28 +0000 (UTC), Jeremy Whitlock
<Jeremy_Whitlock@adp.com> wrote:
> Before I installed WebTools (IBM's version), I was able to have WebLogic
> run internal to Eclipse by setting it up as a Java Application. I would
> set the main class to "weblogic.Server", pass it the proper jvm arguments
> and WebLogic would run inside of Eclipse. I could set breakpoints in any
> java file being ran on the server. Now, when I run the same Debug
> Application, if I set a breakpoint, it will make my webapp not respond
> and
> it never hits the breakpoint. Somehow, WebTools is causing my debugger
> to
> no longer perform as it once did. Has anyone seen this or have any way
> to
> remedy? Thanks, Jeremy
>
Is that with JSP's? Or just Java files? If the former, I might have a wild
guess you could experiment with,
if you'd like. But I don't think what I'm about to say would effect
regular .java files, in which case
I'm not sure what the problem would be.
In the com.ibm.sse.editor.jsp plugin.xml file, you'll see a line as
follows:
class=" com.ibm.sse.editor.jsp.breakpointproviders.JavaStratumBreakp ointProvider:*jsp "
That "*jsp" part was added recently since found to help "debugging
performance" on some servers (well, at least one),
and we know we'll have to make that a "variable" someday depending on the
target server, but "hard coded" for now.
(It basically helps the debugger "pattern match" files to watch to see
when their class files have to be reloaded).
You could trying changng it "back" to just '*', instead of '*jsp' to see
if that helps (and remember, you *may* have to use -clean first time
launching eclipse after making this change. You will of course have to
remove all breakpoints and re-set them. This is mostly a "shot in the
dark" just for JSPs ... just an idea ... sorry I can't guess anything more
definitive.
I'm curious is this helps, or how weblogic server "mangles" its tranlated
JSP names, since we're just beginning to explore all the differnt ways
servers implement this -- and we already know some post-pend and some
pre-pend, so may not be a single pattern that works for all.
|
|
|
| Re: WebTools Killed My Debugger [message #33498 is a reply to message #33431] |
Tue, 27 July 2004 23:41 |
| Eclipse User |
|
|
|
David Williams wrote:
> On Tue, 27 Jul 2004 23:10:28 +0000 (UTC), Jeremy Whitlock
> <Jeremy_Whitlock@adp.com> wrote:
> > Before I installed WebTools (IBM's version), I was able to have WebLogic
> > run internal to Eclipse by setting it up as a Java Application. I would
> > set the main class to "weblogic.Server", pass it the proper jvm arguments
> > and WebLogic would run inside of Eclipse. I could set breakpoints in any
> > java file being ran on the server. Now, when I run the same Debug
> > Application, if I set a breakpoint, it will make my webapp not respond
> > and
> > it never hits the breakpoint. Somehow, WebTools is causing my debugger
> > to
> > no longer perform as it once did. Has anyone seen this or have any way
> > to
> > remedy? Thanks, Jeremy
> >
> Is that with JSP's? Or just Java files? If the former, I might have a wild
> guess you could experiment with,
> if you'd like. But I don't think what I'm about to say would effect
> regular .java files, in which case
> I'm not sure what the problem would be.
> In the com.ibm.sse.editor.jsp plugin.xml file, you'll see a line as
> follows:
>
class=" com.ibm.sse.editor.jsp.breakpointproviders.JavaStratumBreakp ointProvider:*jsp "
> That "*jsp" part was added recently since found to help "debugging
> performance" on some servers (well, at least one),
> and we know we'll have to make that a "variable" someday depending on the
> target server, but "hard coded" for now.
> (It basically helps the debugger "pattern match" files to watch to see
> when their class files have to be reloaded).
> You could trying changng it "back" to just '*', instead of '*jsp' to see
> if that helps (and remember, you *may* have to use -clean first time
> launching eclipse after making this change. You will of course have to
> remove all breakpoints and re-set them. This is mostly a "shot in the
> dark" just for JSPs ... just an idea ... sorry I can't guess anything more
> definitive.
> I'm curious is this helps, or how weblogic server "mangles" its tranlated
> JSP names, since we're just beginning to explore all the differnt ways
> servers implement this -- and we already know some post-pend and some
> pre-pend, so may not be a single pattern that works for all.
David,
It's with *.jsp and *.java. I tried to debug a servlet and it will
just sit there and do nothing if there is a breakpoint in the servlet
where before WebTools, it would stop at the breakpoint for debugging. The
debugger's breakpoint is never met now that WebTools is installed.
Something is keeping the debugger from working and I'm not sure what it
could be. I do assure you that it's only been working like this, or not
working in my case, since I installed WebTools. Still works on an Eclipse
without WebTools. Thanks, Jeremy
|
|
| | | | |
| Re: WebTools Killed My Debugger [message #35221 is a reply to message #34647] |
Fri, 30 July 2004 11:32 |
| Eclipse User |
|
|
|
Tim deBoer wrote:
> Jeremy,
> I'm the other half of the equation (David does JSP editing & breakpoints,
> and I do the server/Tomcat tools), but I'm also stumped at this one. We
> definitely don't do anything that should conflict with debugging, and this
> code has shipped in WebSphere Studio, which has lots of other things that
> integrate with the debugger without problems.
> Do you have any other plugins on top of Eclipse v3.0 that might be
> conflicting, and can you debug a regular Java application? Since the problem
> sounds like a source locator issue, I'd try going to the Source tab of your
> WebLogic Java launch configuration. If there is anything obviously wrong
> (e.g. missing your project in the list of source) you can override it and
> specify exactly which projects you do want on the source lookup path.
> Hopefully this should get you around the problem.
Tim,
I fully agree that this is very wierd and probably not a regular
occurance. I will assist you in any way that I can. I can successfully
debug another project with .java files but they aren't being ran via
WebLogic. I have not changed JREs at all or WebLogic versions either. I
have all the same .jar files on the classpath and I have all the same
folders on the sourcepath. I would be glad to send you any files you'd
need, including screenshots, to help me in coming up with a remedy.
Thanks, Jeremy
|
|
| | |
Goto Forum:
Current Time: Wed Jul 16 18:17:30 EDT 2025
Powered by FUDForum. Page generated in 0.25399 seconds |
Home