[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4497) s:convertPojo key="<fieldName>" component

[deanhiller (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12499801#action_12499801 ] 

deanhiller commented on JBSEAM-4497:
------------------------------------

hmm, well how does the s:convertEntity work in Session scope then.  After the entitymanager is gone from he page render, the list still seems to be in memory because you can have edit actions and when clicked they have to relate back to the same list.  couldn't the cleanup be done just like s:convertEntity for Sessionscope....I don't really need session scope actually.  I just need conversation scope for that one thing I was doing, but I would expect it to behave however s:convertEntity behaves.

> s:convertPojo key="<fieldName>" component
> -----------------------------------------
>
>                 Key: JBSEAM-4497
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4497
>             Project: Seam
>          Issue Type: Feature Request
>          Components: JSF Controls
>    Affects Versions: 2.2.0.GA
>            Reporter: deanhiller
>            Priority: Minor
>
> It would be awesome if we could have an <s:convertPojo key="<unique field>"> component with a key attribute that identifies a unique key in the pojo to do translation with.  ie. s:convertEntity uses the primary key of the entity but convertPojo could be used for entities that are not in the database yet if for instance the name was a unique.  Also, it could just be used for pojos from a webservice or something for that matter.  It could even throw a NonUniqueException if in the list of pojo's it finds two with the same exact key so people use it correctly and an exceptions is thrown when not used correctly so we know.  Anyways, just thought this would be a nice feature add to an already pretty damn sweet toolbox called seam.

-- 
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