|Re: Breakpoints in JSP pages [message #224240 is a reply to message #224232]
||Tue, 25 November 2008 14:36
| Steven Curtis
Registered: July 2009
Nick Sandonato wrote:|
>> I don't have much concrete ... but first, you are intentionally studying
>> the problem with files that have the same name, right? There's some
>> (oldish) bugzilla entries that talk about problems with files that have
>> the same name (but in different directories). You might search bugzilla
>> to see if you can find them, and if so, if they might help explain the
>> issues. [I don't know if they'd be open or closed.] My guess it that it
>> is related to how the jsp name-mangling is done ... but, that is just a
> Here's the (oldish) bug:
> Hope this helps to clear things up a little.
Thanks for the info, but I guessed that might be the problem as well.
I've been able to reproduce the issue using two JSP files with different
file names. To your point, when two files with the same file name are in
different source paths in an OC4J debug session, current Eclipse behavior
is to prompt the user to resolve the ambiguity with a dialog box asking
for which source file to display. Unfortunately, in the jsp/index.jsp
case, the dialog doesn't show because the breakpoint isn't being triggered.
Another curiosity is the fact that the JBoss debug session has absolutely
no problem distinguishing between two files in different directories with
the same name while the OC4J debug session prompts to resolve ambiguities
and will occasionally display the wrong file. Is this due to an
incomplete or buggy JSR 45 implementation in OC4J? Incorrect "jsp
name-mangling" (Not sure what that is. Have any more details?) by OC4J?
I've read about line number maps that are supposed to be passed back to
the IDE. Maybe the maps coming from OC4J are malformed or incomplete?
Still researching. Suggestions appreciated.
Powered by FUDForum
. Page generated in 0.05083 seconds