[
http://jira.jboss.com/jira/browse/JBIDE-1410?page=all ]
Menashe updated JBIDE-1410:
---------------------------
it should be a rather easy fix to just drop
#{facesContext.externalContext.requestContextPath} since when this is removed the editor
works fine
and unless someone knows any other way thne useing
#{facesContext.externalContext.requestContextPath} in the template file, i will like to
hear that, afaik
facelets doesn;t work any other way which makes this a bug not a feature request
el resolution in visual editor
------------------------------
Key: JBIDE-1410
URL:
http://jira.jboss.com/jira/browse/JBIDE-1410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.0.0.CR1
Environment: seam2.0
eclipse 3.3.1.1
Reporter: Menashe
Fix For: 2.1
When el is used (as image/css source) the visual editor doesn't resolve it.
Here is what I mean (this is part of my template therefor it must be full path, since if
it left as relative path it gets resolved based on the path of the page that is using the
template and not of the actual template location.)
<img
src="#{facesContext.externalContext.requestContextPath}/images/header.gif"/>
Visual editor should be able to figure out that
#{facesContext.externalContext.requestContextPath} should be just dropped.
Since
<img src="/images/header.gif"/>
works fine in visual editor but not in the seam2 (unless contextpath is '/')
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira