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.
Summary: | [50cat] StringIndexOutOfBoundsException while editing webapp files | ||
---|---|---|---|
Product: | javaee | Reporter: | jlaskowski <jlaskowski> |
Component: | Code | Assignee: | Marek Fukala <mfukala> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
jlaskowski
2005-09-25 22:01:38 UTC
reassigning to web module I received a similar error while editing an existing JSP. The problem occured just as I was completing a script tag. My build number is 200509251800. The log file showed the following stack trace. [org.openide.text.CloneableEditorSupport] INFORMATIONAL *********** Exception occurred ************ at 8:28 AM on Sep 28, 2005 javax.swing.text.BadLocationException: BaseDocument.write() at org.netbeans.editor.BaseDocument.write(BaseDocument.java:1193) at org.netbeans.editor.BaseKit.write(BaseKit.java:453) at org.netbeans.modules.web.core.jsploader.BaseJspEditorSupport.saveFromKitToStream(BaseJspEditorSupport.java:263) [catch] at org.openide.text.CloneableEditorSupport.getInputStream(CloneableEditorSupport.java:1221) at org.netbeans.modules.web.core.jsploader.JspParserAccess$WM.getEditorInputStream(JspParserAccess.java:84) at org.netbeans.modules.web.jspparser.ParserServletContext.getResourceAsStream(ParserServletContext.java:283) at org.apache.jasper.JspCompilationContext.getResourceAsStream(JspCompilationContext.java:262) at org.apache.jasper.compiler.JspUtil.getInputStream(JspUtil.java:834) at org.apache.jasper.xmlparser.XMLEncodingDetector.getEncoding(XMLEncodingDetector.java:105) at org.apache.jasper.compiler.ParserController.determineSyntaxAndEncoding(ParserController.java:304) at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:169) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:100) at org.apache.jasper.compiler.GetParseData.parse(GetParseData.java:122) at org.netbeans.modules.web.jspparser_ext.WebAppParseSupport$3.run(WebAppParseSupport.java:660) *********** Exception occurred ************ at 8:28 AM on Sep 28, 2005 java.lang.StringIndexOutOfBoundsException: String index out of range: 3 at java.lang.String.substring(String.java:1765) at org.netbeans.modules.web.core.syntax.completion.JspCompletionQuery.queryJspDirectiveInContent(JspCompletionQuery.java:464) at org.netbeans.modules.web.core.syntax.completion.JspCompletionQuery.query(JspCompletionQuery.java:93) at org.netbeans.modules.web.core.syntax.completion.JspCompletionProvider.queryImpl(JspCompletionProvider.java:134) at org.netbeans.modules.web.core.syntax.completion.JspCompletionProvider$Query.query(JspCompletionProvider.java:76) at org.netbeans.spi.editor.completion.support.AsyncCompletionTask.run(AsyncCompletionTask.java:181) at org.openide.util.Task.run(Task.java:207) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:469) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:870) The abbreaviations completion provider has been removed so the first problem is obsolete now. As for the second (SIOOB from JSP CC) - can you be more specific? Add a particular situation when the problem happended? The CC for JSP directives normally works without problems so we need a some steps to reproduce. I guess the SIOOB issue has already been likely fixed by my fix of Issue #65094 (SIOOB for JSP tag CC on the last line). I am leaving the issue opened for some time - please verify whether you are still able to reproduce, and if so, add a build number and some more info when it happens. Thanks. Very likely already fixed by fix of Issue #65094. If you can reproduce on a latest build, feel free to reopen. |