It's actually pretty easy, and you don't want to have your back-end objects tightly coupled to your front-end objects. Your back-end objects typically should not have any concept of "selections."
- Brendan -----Original Message----- From: Rick Reumann [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 12:43 PM To: MyFaces Discussion Subject: Re: Best way to use object properties from a List to create Select Items? On 9/8/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote: > BTW, the List (or, more generally, the Collection) is assumed to contain > SelectItem instances. Ok, I guess I'll have to make methods to covert my Collections to new Collections/Maps or probably just convert them to a SelectItem[] array. This is one area that I believe will/should need to be addressed moving forward. Often times Collections are brought back from backend methods that are already in place and the developers are forced to use. It's now pretty a much a pain to have to call dackend.getAnimals(), backend.getEmployees(), backend.getCollectionOfFooBars(), only to have to then convert that Collection into something that can be used nicely by the front end for select options. When I finally get up to speed with this stuff, I'll see if I can help contribute a tag to help.
