"JSF EL out of attribute" error using 6.0 release

Bug was fixed in 6.0.1

Ray DeCampo wrote:

Hello,

I am evaluating IntelliJ 6.0 for use on a facelets project. Currently I get "JSF EL out of attribute" errors from IDEA for snippets like the following in an .xhtml file:

 
>     I am thinking of a number from #{numberBean.min} 
>     to #{numberBean.max}.  Can you guess it?
>   
> ]]>

I have *.xhtml mapped to JSPx file type as suggested in another post on the forum.

I thought that I saw a closed bug on this issue, so I was surprised to see it is still a problem after the beta. Which makes me think it may just be something I am doing.

Anyone have any ideas?

Thanks,
Ray

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

I'm using 6.0.1 now (build 5784), and I just noticed that I still get this error. Perhaps I am doing something wrong, but it is not obvious to me.

In 6.0.2 we fixed this issue appearing during edit of facelets files

Ray DeCampo wrote:

I'm using 6.0.1 now (build 5784), and I just noticed that I still get this error. Perhaps I am doing something wrong, but it is not obvious to me.

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Thanks, you guys do a great job.

Are there any plans to address the "JSF component tag h:xyzzy outside view tag" warning message that I see when doing facelets?

This can be solved with the <ui:composition> facelet tag. Wrap that tag around the part of the facelet file which will actually be inserted into the other page. Facelets will ignore everything outside the <ui:composition> tag. So to make IDEA happy, put the <f:view> tag outside the <ui:composition>.

We also put an <f:loadBundle> tag in all our facelet fragments, outside the <ui:composition>, which lets IDEA validate our labels['...'] statements.

I'm using 6.05, not using facelets, and getting this error for no reason I can discern. Making a "friendly" error page to trap 404 and 500, etc. Built a backing bean to supply the message and the stack trace, but those values are not recognized in the jsp.

Are there likely candidates for something I missed wiring things together?

===== from errorPage.jsp ===
Oops!
Here is the stack Trace:
]]>

I was experiencing this same problem. I'm using 6.0.5. I blew away my web module and started from scratch but that didn't seem to resolve it. But it looks like I did find a workaround.

We include pointers to all of our taglibs at the top of our JSPs. So:
<%@ include file="/en/jstl/taglibs.jsp" %>

I removed the "/" to "en/jstl/taglibs.jsp" and the inspector red-flagged it. When I added the slash back in "/en/jstl/taglibs.jsp", it resolved all the tags and resolved all the "JSF EL out of attribute" warnings.

Hopefully this helps in some way.

Joe Miller