[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-5961) JSF EL Code complition doesn't recognize static methods.

[Victor Rubezhny (JIRA)]

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

Victor Rubezhny resolved JBIDE-5961.
------------------------------------

    Resolution: Done


Fix enables the static methods to be present as EL operands for Seam/CDI-enabled projects, but disables them for JSF projects. The validation is consistent with the Content Assist, so, a warning will be shown for static methods in JSF projects, but validation will say OK for the static methods in Seam or CDI-enabled projects 

> JSF EL Code complition doesn't recognize static methods.
> --------------------------------------------------------
>
>                 Key: JBIDE-5961
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5961
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JSF
>    Affects Versions: 3.1.0.CR2
>            Reporter: Alexey Kazakov
>            Assignee: Victor Rubezhny
>             Fix For: 3.1.0.CR3
>
>         Attachments: patch_JBIDE-5961.txt
>
>
> 1. @Name("searchTools")
> public class SearchTools
> {
>    public static String getClassName(Object object)
>    {
>       if(object.getClass().getSimpleName().contains("$$"))
>       {         
>          return object.getClass().getSuperclass().getSimpleName();
>       }
>       else
>       {
>          return object.getClass().getSimpleName();
>       }
>    }   
> }
> 2. There should be #{searchTools.getClassName()} proposal in CA.
>     For example: <h:outputText value="Organization" rendered="#{searchTools.getClassName(result) == 'Organization'}" />

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira