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 227589 - Error parsing jsp file error message
Summary: Error parsing jsp file error message
Status: RESOLVED DUPLICATE of bug 225442
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-17 23:55 UTC by jaycverg
Modified: 2013-03-18 07:25 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (65.00 KB, text/plain)
2013-03-17 23:55 UTC, jaycverg 		Details
screenshot (164.19 KB, image/png)
2013-03-17 23:56 UTC, jaycverg 		Details
sample jsp code (10.10 KB, application/octet-stream)
2013-03-17 23:57 UTC, jaycverg 		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 jaycverg 2013-03-17 23:55:12 UTC 
This issue happens only on the project explorer. It says that "Error Parsing JSP File" with a red exclamation mark icon, but when I open the file there is  no error at all. There are no lines underlined with red or sytanx error on the code.


Product Version = NetBeans IDE 7.3 (Build 201302132200)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.6.0_34
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.9-b04
Comment 1 jaycverg 2013-03-17 23:55:17 UTC 
Created attachment 132736 [details]
IDE log
Comment 2 jaycverg 2013-03-17 23:56:03 UTC 
Created attachment 132737 [details]
screenshot
Comment 3 jaycverg 2013-03-17 23:57:26 UTC 
Created attachment 132738 [details]
sample jsp code
Comment 4 Martin Fousek 2013-03-18 07:25:11 UTC 
This should be duplicate of issue #225442. Please give it a try in the latest development builds, it should work well to you there (should be also fixed in the first patch).

*** This bug has been marked as a duplicate of bug 225442 ***