Project
IntelliJ IDEA
Priority
Normal
Type
Bug
Fix versions
No Fix versions
State
Fixed
Assignee
Maxim Mossienko
Subsystem
Editor. Error Highlighting
Affected versions
No Affected versions
Fixed in build
108.65  
  • Created by   Raymond DeCampo
    5 years ago (09 Dec 2006 00:44)
  • Updated by   root
    2 years ago (17 Jan 2010 20:38)
  • Jira: IDEADEV-12512
    (history, comments)
 
IDEA-35892 href and image src attributes incorrectly labelled invalid
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
In a facelets project we use the following code to create links or source images within an XHTML file:

<img src="#{facesContext.externalContext.requestContextPath}/images/blah.gif"/>

IDEA incorrectly reports "Cannot resolve symbol..." even though the file exists in the correct location. The same issue happens with href in anchor tags.

I understand the difficulty in generic parsing of EL expressions within tags like this but perhaps the #{facesContext.externalContext.requestContextPath} idiom could be handled specially as it is common.


Environment: Windows 2000

Issue was resolved
Comments (5)
 
History
 
Linked Issues (?)
 
Maxim Mossienko
  Maxim Mossienko
09 Dec 2006 01:05
5 years ago
Have you mapped xhtml extension to JSPX file type?
Raymond DeCampo
  Raymond DeCampo
09 Dec 2006 01:10
5 years ago
Yes; I unmapped .xhtml from XHTML and assigned it to the JSPX file type.

Other things are working without issue, just this aspect.
Taras Tielkes
  Taras Tielkes
09 Dec 2006 01:31
5 years ago
Sounds similar to (but different from): IDEA-30613
Taras Tielkes
  Taras Tielkes
11 Dec 2006 17:25
5 years ago
Does this fix for this provide completion after the #{facesContext.externalContext.requestContextPath} part?
In other words: does the editor understand that #{facesContext.externalContext.requestContextPath} maps to the context root?

If so, then adding similar support for the non-JSF variant ${pageContext.request.contextPath} would be a first step to the fix for IDEA-30613
Maxim Mossienko
  Maxim Mossienko
11 Dec 2006 18:00
5 years ago
No, the fix removes erroneous highlighting for {...} having been recognized as an anchor reference.