[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-129) JSF SelectItems automatic Converter creation using a @Selectable annotation
Gavin King (JIRA)
jira-events at lists.jboss.org
Mon Feb 26 18:30:35 EST 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-129?page=all ]
Gavin King closed JBSEAM-129.
-----------------------------
Resolution: Out of Date
Assignee: Pete Muir
Pete Muir's stuff supercedes this old issue.
> JSF SelectItems automatic Converter creation using a @Selectable annotation
> ---------------------------------------------------------------------------
>
> Key: JBSEAM-129
> URL: http://jira.jboss.com/jira/browse/JBSEAM-129
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: JSF
> Environment: Jboss Application Server using Myfaces jsf and Seam from CVS
> Reporter: James Salt
> Assigned To: Pete Muir
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> The entity class annotated with @Selectable would have to have an @Id attribute and a attribute annotated with something like @SelectionName for the displayed name of the object in the selectItems.
> The converters for each @Selectable entity could be created and cached at seam scanner time for each entity component that had @Selectable annotation. This scanner task would also need to dynamically register the converters with jsf/myfaces which I believe is possible using the myfaces Application class (don't know about the RI implementation).
> The user would be responsible for the creation of the list of objects (Seam supplying a static method to convert a list of objects to a list of select items), then the converters would deal with converting the selected item back to the object using a direct database lookup.
> As mentioned in the below thread, the object marked as @Selectable would need to implement a custom equals operation (being careful about @Datamodel update issues), so that myfaces could validate it correctly.
> For reverese engineering purposes, anything that has a field of a certain object would infer that that object is selectable, then the user could customise which field is used for the @Selectionname annotation. This would be very valuable when reverse engineering, and would remove a significant coding burden from the Seam developer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list