This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 133668 - java.net.MalformedURLException: unknown protocol: javascript
Summary: java.net.MalformedURLException: unknown protocol: javascript
Status: RESOLVED INCOMPLETE
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Quy Nguyen
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-22 14:19 UTC by Lukas Jungmann
Modified: 2008-04-28 13:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 48777


Attachments
stacktrace (2.69 KB, text/plain)
2008-04-22 14:19 UTC, Lukas Jungmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2008-04-22 14:19:30 UTC
Build: NetBeans IDE 6.1 (Build 200804211638)
VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02
OS: Linux, 2.6.22-14-generic, i386

User Comments: 
-double-click on the breakpoint in the Breakpoints window (I think)

=> MalformedURLException: unknown protocol: javascript
Comment 1 Lukas Jungmann 2008-04-22 14:19:37 UTC
Created attachment 60555 [details]
stacktrace
Comment 2 Lukas Jungmann 2008-04-22 14:26:30 UTC
you might want to check also maybe similar issue 125694 which has been fixed for 6.1 (related to debugging jsp)
Comment 3 Quy Nguyen 2008-04-22 19:15:31 UTC
Could you give a reproducible test case for this?  I don't know how a URI with the 'javascript' protocol could be
created and used in the breakpoints window.
Comment 4 Lukas Jungmann 2008-04-22 20:37:27 UTC
I'd be really happy if I find it (I mean reproducible test case). Problem is that once this exception happens it is
sometimes not easy to get rid of it (similarly as in case of issue 125694).

I've got it also after pressing "Continue" in IDE's toolbar when debugger stopped on the breakpoint.
Comment 5 Lukas Jungmann 2008-04-22 20:38:06 UTC
btw: is there some logging I could turn on?
Comment 6 Lukas Jungmann 2008-04-22 20:44:02 UTC
also from http://statistics.netbeans.org/analytics/detail.do?id=48777 it seems that exception was thrown after "Step
Over" action but not all user actions are being logged...
Comment 7 Quy Nguyen 2008-04-22 20:59:52 UTC
Could you describe what you were doing in general before the exception occurred, e.g. the project you were working with,
the breakpoints that were set (which file types and what locations in those files), etc?
Comment 8 Quy Nguyen 2008-04-22 21:00:57 UTC
For logging, you could change the logging level of the web.client.javascript.debugger.api module, but I don't know if
you will get much more information.
Comment 9 Lukas Jungmann 2008-04-28 13:52:35 UTC
I still haven't found any reproducible steps for this :( => P3