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: | Missing contextPath in EL code competion | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Petr Pisl <ppisl> |
| Component: | JSP | Assignee: | issues@javaee <issues> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
Taking over javax.servlet.jsp.PageContext.getRequest() formally returns ServletRequest and not HTTPServletRequest, which has the field contextPath. Can we really assume PageContext.getRequest() is always HTTPServletRequest? And if so is it worth the hack? Tomasz, you are right. On the other hand 99% of the request are HTTPServletRequest in jsp/html pages. So I think it worth doing this hack. Probably we should somehow mark these items in the code completion window to users know, that this is HTTPServletReqeust. Do you think, that this is doable in a way? It is doable, although I am not keen on doing it. Are you aware of other situations like this? We could think of a general mechanism. Changing issue type to enhancement. Obsolete milestone, please reevaluate This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss |
The request property of pageContext should also offer context path in cc (${pageContext.request.|}). So the result should be ${pageContext.request.contextPath}