[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3419) Conversational DataModel is not working properly
Pete Muir (JIRA)
jira-events at lists.jboss.org
Mon Sep 15 11:26:21 EDT 2008
[ https://jira.jboss.org/jira/browse/JBSEAM-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir closed JBSEAM-3419.
-----------------------------
Fix Version/s: (was: 2.0.3.CR2)
Resolution: Rejected
Please ask for help on the forums at http://www.seamframework.org
> Conversational DataModel is not working properly
> ------------------------------------------------
>
> Key: JBSEAM-3419
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3419
> Project: Seam
> Issue Type: Feature Request
> Components: AOP
> Affects Versions: 2.0.3.CR1
> Environment: All environments
> Reporter: Maximiliano Carrizo
>
> DataModel outjecting the very first value instead of selected one.
> Example source code:
> @Name("permissionRolesSearch")
> @Scope(ScopeType.CONVERSATION)
> @Restrict("#{identity.loggedIn}")
> @Conversational
> public class PermissionRolesAction implements PaginatorListener,Serializable {
>
> /**
> *
> */
> @DataModel
> PaginatorList<PermissionRoles> permissionRolesList;
> ...........................
> ...........................
> PaginatorList implements List, and with SESSION scope works fine.
> When I have a bean in Conversational Scope, and this bean has a DataModel, it has two problems.
> 1) outjecting the very first value instead of selected one
> 2) if outjected object is different from ArrayList, app throws an IllegalArgumentException.
> This is an example of Seam Debug Page in the last case:
> class class org.jboss.seam.jsf.ListDataModel
> dataModelListeners []
> rowAvailable false
> rowCount 10
> rowData java.lang.IllegalArgumentException[null]
> rowIndex -1
> wrappedData it.ma.dpn.util.view.PaginatorList at 843edc
> toString() org.jboss.seam.jsf.ListDataModel at 1297ba3
> You can see a better description in:
> http://seamframework.org/Community/DataModelOutjectingTheVeryFirstValueInsteadOfSelectedOne
> P.S.1 I cant set ScopeType.CONVERSATIONAL, because it isnt allowed.
> P.S.2 Setting SESSION context it isnt satisfactory, because bean stays active, and it isnt desired behavior.
--
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
More information about the seam-issues
mailing list