| f:loadBundle doesn't contibute it's "var" variable to EL [message #474194] |
Fri, 25 May 2007 22:40  |
Eclipse User |
|
|
|
Hi!
I got some problem with EL contribution for loadbundle tag.
Contribution works fine for h:datatable or tomahawk library tags through
extension plugin, but for f:loadBundle it doesn't. Here is simple jsf page
source:
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<html>
<body>
<f:view>
<f:loadBundle var="msg" basename="com.test.msg" />
<h:outputText value="#{}" />
</f:view>
</body>
</html>
...and com.test.msg.properties contains single entry.
When i open content assist for EL expression in h:outputText - "msg" var
is not there. Maybe contribution for loadbundle just isn't implemented at
all and i search for a black cat in a dark room? :)
P.S.
JSF implementation is myfaces 1.1.5 (if it really matters at all). I fresh
installation of eclipse3.3 rc1, wtp2.0 rc1 and clean workspace, but with
no luck.
Thanks!
|
|
|
| Solved my problem, but don't know, should it be considered as a bug or not [message #474195 is a reply to message #474194] |
Sun, 27 May 2007 22:33  |
| Eclipse User |
|
|
|
Solved my problem: extension of jsp file with jsf tags was "jsf" instead
of "jsp" (configured URL mapping pattern for project is "*.jsf" instead of
default "/faces/*", so i tangle extensions sometimes). If file has "jsp"
extension everything works fine.
That error seems to be ok, since JSF pages are all jsp at their base, so
they all must by named "*.jsp". But WTP, when installed, defines some more
file extensions bound to JSP file editor: jsf, jspf and jspx.
Should all JSF Tools content assist functionality be available for files
with these extensions (i.e. jsf)? Or should it be available only for *.jsp
files?
I don't know, should it be considered as a bug (and reported) or as a
feature (and be left as-is) :)
Hope you'll help me find answer for these questions.
Thanks for your attention again!
|
|
|
|
| Solved my problem, but don't know, should it be considered as a bug or not [message #610970 is a reply to message #474194] |
Sun, 27 May 2007 22:33 |
| Eclipse User |
|
|
|
Solved my problem: extension of jsp file with jsf tags was "jsf" instead
of "jsp" (configured URL mapping pattern for project is "*.jsf" instead of
default "/faces/*", so i tangle extensions sometimes). If file has "jsp"
extension everything works fine.
That error seems to be ok, since JSF pages are all jsp at their base, so
they all must by named "*.jsp". But WTP, when installed, defines some more
file extensions bound to JSP file editor: jsf, jspf and jspx.
Should all JSF Tools content assist functionality be available for files
with these extensions (i.e. jsf)? Or should it be available only for *.jsp
files?
I don't know, should it be considered as a bug (and reported) or as a
feature (and be left as-is) :)
Hope you'll help me find answer for these questions.
Thanks for your attention again!
|
|
|
|
Powered by
FUDForum. Page generated in 0.27677 seconds
Home