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 133939 - parsing web-app project generates javax.swing.text.BadLocationException
Summary: parsing web-app project generates javax.swing.text.BadLocationException
Status: RESOLVED FIXED
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-25 14:38 UTC by gord
Modified: 2009-02-27 14:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
NB Log file showing BadLocationException stack traces (2.59 MB, text/plain)
2008-04-25 14:40 UTC, gord 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gord 2008-04-25 14:38:31 UTC 
Opening web project that includes dojo v1.1.0 generates > 100 javax.swing.text.BadLocationException exceptions.  I will
attach the log file (2.5MB).

The project is a Struts (v1.2.9) based web app depending on 2 java library projects.  The target web server is Tomcat
5.5.26 running JDK 1.5.0_14 x64 (AMD).  All the projects are set to use this JDK (v1.5) as their target platform.

NB61 RC2 is running JDK 1.6.0_04 x64 (AMD) on a WinXP x64 2003 Edition SP2 machine.

This project was originally developed using NB55, migrated to NB551, NB601, then tried on NB61RC1 and RC2.
Comment 1 gord 2008-04-25 14:40:18 UTC 
Created attachment 60696 [details]
NB Log file showing BadLocationException stack traces
Comment 2 Torbjorn Norbye 2008-04-26 06:57:18 UTC 
I checked in a fix for this in changeset http://hg.netbeans.org/main/rev/34a5f55fb030 which will be included in build
1742 from http://deadlock.netbeans.org/hudson/job/trunk/ .
Comment 3 gord 2008-04-29 15:08:21 UTC 
Any chance this fix will be backported to 6.1?
Comment 4 Martin Schovanek 2008-05-07 09:37:14 UTC 
The fix should be available on update center soon.
Comment 5 pslechta 2008-05-15 11:30:04 UTC 
The fix has been ported into the release61_fixes repository.

See Issue 135059 for more details.