Right, this is how the Seam 2 convertor worked. It used an abstraction over JPA providers (to give us extra hooks, maybe not needed now in JPA 2) to extract the id of an entity (as you can't rely on the annotation as there is xml as well). It then use a unique id generator to put that into the form as an id, and stored a map that attached the database id to this unique id (this prevented leaking database ids to the UI).
It worked pretty well in the end. On 19 Aug 2013, at 15:49, Arne Limburg <arne.limb...@openknowledge.de> wrote: > Hmm, > > > Anyway, with an EntityManager we could identify the id field of the entity > and convert the entity to its id and vice versa. This could be useful for > lists or select menus. > > Am 19.08.13 16:35 schrieb "Jason Porter" unter <lightguard...@gmail.com>: > >> Hm, I'll have to go back to the code to see what was done. >> >> >> On Mon, Aug 19, 2013 at 5:06 AM, Pete Muir <pm...@redhat.com> wrote: >> >>> The Seam 2 converter worked on any entity class, you just had to provide >>> it with a reference to the EntityManager. >>> >>> On 18 Aug 2013, at 05:16, Jason Porter <lightguard...@gmail.com> wrote: >>> >>>> The problem with a generic JSF converter is that it has to be very >>> dumb, >>> or you have to use a certain kind of object. >>>> >>>> >>>> >>>> >>>> >>>> The Seam 3 converter went as generic as possible, it also kept >>> things >>> in the conversion (and should work fine in the request as a >>> conversation is >>> at least as long as a request). Depending on what state you're storing >>> in >>> the converter, you probably wouldn't want anything longer than the >>> conversation due to memory issues. >>>> >>>> >>>> >>>> >>>> >>>> If memory serves correctly, the Seam 2 converter really only worked >>> if you were using the EntityHome classes. >>>> >>>> >>>> >>>> >>>> >>>> If you were to do anything similar to the Seam 2 converter you'd >>> need >>> to create some sort of object hierarchy the user would need to use, or >>> try >>> to perform some sort of generic magic with the criteria API, which is >>> not >>> the easiest of things to do. >>>> >>>> >>>> >>>> >>>> >>>> All that being said, I'd be happy to talk ideas out anyone may >>> have. >>>> >>>> ‹ >>>> Sent from Mailbox for iPhone >>>> >>>> On Sat, Aug 17, 2013 at 7:51 PM, hantsy <han...@yahoo.com.cn> wrote: >>>> >>>>> I have posted some content on JBoss.org forum before....the Seam3 >>> faces >>>>> object converter does not work well as the Seam 2 one. >>>>> The Seam 3 only works in a conversation(the view is a conversation), >>> and >>>>> it also does not support @ManytoMany. >>>>> The Seam2 version works perfectly....it works in request, >>> conversation >>>>> and other scopes...the better is when I used multi check box...it can >>>>> deal with the Hibernate/JPA @ManyToMany relation correctly with any >>>>> codes in the backend codes when I selected or unselected an option. >>>>> Hantsy >>>>> On 8/18/2013 05:42, Adrian Gonzalez wrote: >>>>>> Hi, >>>>>> >>>>>> In the meantime, if you're looking for a JSF converter, you can >>> take a >>> look at Omnifaces SelectItemsConverter [1]. >>>>>> >>>>>> Regards, >>>>>> Adrian >>>>>> >>>>>> [1] http://showcase.omnifaces.org/converters/SelectItemsConverter >>>>>> >>>>>> >>>>>> ________________________________ >>>>>> De : Mark Struberg <strub...@yahoo.de> >>>>>> À : "dev@deltaspike.apache.org" <dev@deltaspike.apache.org> >>>>>> Envoyé le : Vendredi 16 août 2013 12h39 >>>>>> Objet : Re: General Converter >>>>>> >>>>>> >>>>>> Hi Florian! >>>>>> >>>>>> Not yet on our list. We are currently working on getting 0.5 out of >>> the door (code reviews and testing against many containers) >>>>>> >>>>>> >>>>>> Please file a feature request in JIRA describing what this Seam2 >>> feature is about and why you like it. >>>>>> >>>>>> >>>>>> txs and LieGrue, >>>>>> strub >>>>>> >>>>>> >>>>>> >>>>>> ----- Original Message ----- >>>>>>> From: "i...@softwareentwicklung-hell.de" < >>> i...@softwareentwicklung-hell.de> >>>>>>> To: dev@deltaspike.apache.org >>>>>>> Cc: >>>>>>> Sent: Tuesday, 13 August 2013, 14:35 >>>>>>> Subject: General Converter >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> is there a plan to implement Seam like general Converter like the >>> Seam >>>>>>> Faces Object converter? I know it is not really a cdi topic, but >>> there >>>>>>> is still a big gap between what Seam was providing and what >>> DeltaSpike >>>>>>> does. >>>>>>> >>>>>>> Thanks and Regards >>>>>>> Florian >>> >>> >> >> >> -- >> Jason Porter >> http://en.gravatar.com/lightguardjp >
