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 123139 - Java code completion does not work for the JSPWiki applicaiton
Summary: Java code completion does not work for the JSPWiki applicaiton
Status: RESOLVED DUPLICATE of bug 144382
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomasz Slota
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-30 13:43 UTC by Petr Jiricka
Modified: 2008-10-08 10:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
JSPWiki as a NetBeans project (6.54 MB, application/x-compressed)
2007-11-30 14:02 UTC, Petr Jiricka 		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 Petr Jiricka 2007-11-30 13:43:21 UTC 
1. Register GlassFish
2. Open the attached project
3. Open a JSP page with scriptlets, e.g. Comment.jsp
4. Place the caret at the following position in scriptlet:
    WikiEngine wiki = WikiEngine.|
5. Press Ctrl + Space

=> no relevant completion items are displayed
Comment 1 Petr Jiricka 2007-11-30 14:02:31 UTC 
Created attachment 53715 [details]
JSPWiki as a NetBeans project
Comment 2 Tomasz Slota 2008-02-27 17:30:54 UTC 
This problem is caused by the JSP parser failure (Failed to load or instantiate TagExtraInfo class: com.ecyrd.jspwiki.tags.AttachmentsIteratorInfo). Actually  
possibly there are 2 problems here:

1) the TLD library is not found/not parsed
2) the JSP parser should be able to recover from such a situation and provide information that is not directly related to the missing library

the investigation to be continued...
Comment 3 Tomasz Slota 2008-10-08 10:46:29 UTC 
CC works after building the project. Originally it does not work due to the parser failure. It should be definitely made more obvious to the end user, see issue 144382. Also I filed enhancement issue 149476 for pre-compiling classes required by the parser.

When re-evaluating this issue I also discovered a potential problem in the JavaScript editor, reported as issue 149470.

I am closing this as a duplicate of bug 144382, which covers the most important part of this issue (no clear message to the user).

*** This issue has been marked as a duplicate of 144382 ***