[
https://issues.jboss.org/browse/JBIDE-10022?page=com.atlassian.jira.plugi...
]
Victor Rubezhny commented on JBIDE-10022:
-----------------------------------------
The problem with EclipseUIUtil.isOpenInActiveEditor(IFile) described above can occur only
when stepping in debugger over this method. In regular runs there is no such problem (Or
you may setup a breakpoint after EclipseUIUtil.isOpenInActiveEditor(IFile) is returned its
value and run debugger over the call to EclipseUIUtil.isOpenInActiveEditor(IFile) to see
that it works fine).
Multiple problem markers on the same broken EL
----------------------------------------------
Key: JBIDE-10022
URL:
https://issues.jboss.org/browse/JBIDE-10022
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Reporter: Alexey Kazakov
Assignee: Victor Rubezhny
Priority: Critical
Fix For: 3.3.0.Beta1
EXECUTE: Create a jsf kickstart project (2.0)
EXECUTE: Open greeting.xhtml
EXECUTE: Change #{msgs.greeting} to #{msgs.greeting1}. Save the file.
FAILURE: See Problems View. There are four warning messages instead of the only one.
I see there at lease two problems. First at all it seems that
EclipseUIUtil.isOpenInActiveEditor(IFile) doesn't work anymore. It returns false for
any file even if it is open in an active editor. So we use the cached page context of the
file when we are editing it. This is a bug.
Second issue is that our PageContextFactory returns a context with many duplicated EL
references for the same EL. It causes multiple problem markers for the same EL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira