[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-7975) jsf validation gives property does not exist warning on messagebundle properties

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Tue Dec 21 19:31:17 EST 2010


     [ https://issues.jboss.org/browse/JBIDE-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov updated JBIDE-7975:
----------------------------------

         Assignee: Victor Rubezhny  (was: Alexey Kazakov)
    Fix Version/s: 3.2.0.CR1
         Priority: Major  (was: Minor)


> jsf validation gives property does not exist warning on messagebundle properties
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-7975
>                 URL: https://issues.jboss.org/browse/JBIDE-7975
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsp/jsf/xml source editing
>    Affects Versions: 3.2.0.Beta2
>            Reporter: erik van altena
>            Assignee: Victor Rubezhny
>             Fix For: 3.2.0.CR1
>
>
> I have one issue that I did not have with beta 1. In my facelets pages (jsf 1.2 capabilities) I use a message bundle (loaded through f:loadBundle) that I reference like "#{msg.keyname}". Since beta 2 the validator flags all the message bundle properties as non-existing; that did not happen before the update. After changing the references to the map way, as "#{msg['keyname']}", the validator was happy again. 
> It does not happen for all my files; I have a set of richfaces modal panels that I include using facelets ui:include, stored in a separate subdirectory. These did not trigger any validation errors. Seems it only happens for files I reference in the jsf navigation rules. Although I did get the issue in a facelets template also.
> Just to make it clear: I was using beta 1 and had no problems. Upon updating my installed plugins I got beta 2 and after rebooting Eclipse this issue instantly popped up without any changes to the project. I tried the following without success:
> - clean the project
> - manually validate the entire project
> - change the JSF validation settings

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list