Some JSF anomalies

Hi,

How 'mcsmsg' defined (something like <f:loadBundle var="mcsmsg"/>)?
If yes then both issues should be fixed in next EAP build.
If no, then only last issue is fixed and we need to see definition for
mcsmsg

Grant Smith wrote:

Firstly, thanks for the JSF support! One more reason to love IDEA.

Here are two anomalies I have encountered:

1. I18N doesnt seem to be supported yet (see attached screenshot).
2. Datatable variables are not resolved (see same screenshot).


------------------------------------------------------------------------

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

Yes, in a loadbundle !

Most excellent - I look forward to the next release :)

One other small problem I've discovered (not sure if it's fixed in the next build):

If your backing bean extends another java class, then the properties in the base class are not recognized in the .jspx (highlighted in red).

Thanks,
Grant.

OK build 5218 looks MUCH better !!

However, I'm still getting one small problem.. Look at the attached screenshot. You'll see a property is not recognized in one attribute, yet it is recognized in another slightly above it.


Thanks,
Grant

It looks like the problem is specific to the "rendered" attribute.

See new screenshot.


Thanks,
Grant

http://www.jetbrains.net/jira/browse/IDEADEV-5527 -- Fixed

Grant Smith wrote:

OK build 5218 looks MUCH better !!

However, I'm still getting one small problem.. Look at the attached screenshot. You'll see a property is not recognized in one attribute, yet it is recognized in another slightly above it.


Thanks,
Grant


------------------------------------------------------------------------

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

Thanks :)

OK, Build #5231 has some redness in the for= attribute too. See screenshot.

Thank you.
Fixed.

Grant Smith wrote:

Thanks :)

OK, Build #5231 has some redness in the for= attribute too. See screenshot.


------------------------------------------------------------------------

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

Apparently not in #3245. Still problems with the for= attribute. Screenshot attached.

In addition to this, in faces-config.xml, IDEA is insisting on captal first letters for bean scope (Request, Session, Application, None) and will in fact not deploy the xml file if there are errors (It dies in the compilation stage - which is odd because theres no compiling to be done in faces-config.xml :)


Unfortunately, the JSF spec requires the scopes to be all lowercase.

Message was edited by:
Grant Smith

Hi,

Failed to reproduce with simple code, could you, please, attach complete
nonworking code?

Grant Smith wrote:

Apparently not in #3245. Still problems with the for= attribute. Screenshot attached.


------------------------------------------------------------------------

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

Hi,

Does this happen during editing xml or using visual interface?

Grant Smith wrote:

In addition to this, in faces-config.xml, IDEA is insisting on captal first letters for bean scope (Request, Session, Application, None) and will in fact not deploy the xml file if there are errors (It dies in the compilation stage - which is odd because theres no compiling to be done in faces.xml :)


Unfortunately, the JSF spec requires the scopes to be all lowercase.

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