[jbosstools-issues] [JBoss JIRA] (JBIDE-4870) Support suggestions for JSF DataModel when created inline in seam

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen resolved JBIDE-4870.
----------------------------------------

    Resolution: Out of Date


Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).

If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.

Thank you!


                
> Support suggestions for JSF DataModel when created inline in seam
> -----------------------------------------------------------------
>
>                 Key: JBIDE-4870
>                 URL: https://issues.jboss.org/browse/JBIDE-4870
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: seam2
>    Affects Versions: 3.1.0.M3
>         Environment: Seam 2.2.0, Richfaces 3.3.1, Tools 3.1M3, Eclipse 3.5
>            Reporter: Cody Lerum
>            Assignee: Alexey Kazakov
>            Priority: Minor
>             Fix For: LATER
>
>
> When editing an xhtml file if I create a rich:dataTable and use an object outjected via @DataModel then Tools will suggest the possible values for auto-completion. 
> However, if I create the DataModel inline by wrapping a collection like this:
> <rich:dataTable  id="banList" var="ban" value="#{dataModels.getDataModel(summaryBillingAccountNumber.billingAccountNumbers)}" ">
> 	....                                                                                 
> </rich:dataTable>
> Then if I access the value "ban" through EL like <h:outputText value="#{ban.name}" /> the suggestions after I type "ban." are for the DataModel object not the ban object. It would be nice if the behavior was the same.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira