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: | JPQL not parsed, no code completion | ||
|---|---|---|---|
| Product: | javaee | Reporter: | bht <bht> |
| Component: | Persistence | Assignee: | Sergey Petrov <sj-nb> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 7.3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | Maven project with example JPQL in entity | ||
*** This bug has been marked as a duplicate of bug 212951 *** |
Created attachment 130975 [details] Maven project with example JPQL in entity It appears that under some conditions JPQL is not parsed and no code completion hints are available. Please see in the attached example, CustomerOrder.java The remaining files in the project are not relevant. Perhaps the condition that is relevant here has other effects, too. I notice that since JPQL parsing was addded, the IDE is much slower but that might be a coincidence. I would still prefer that JPQL support becomes an optional module.