Finally dove into the code and saw what you were claiming... Under your layout, the path to least resistance may be to use separate Thing objects for the new and the already existent... It's true that the current approach isn't going to work the way you want...
Regards. -----Mensaje original----- De: Mike McNally [mailto:[email protected]] Enviado el: lunes, 19 de enero de 2009 12:40 Para: Stripes Users List Asunto: Re: [Stripes-users] Problem withDefaultActionBeanPropertyBinderandObject value On Mon, Jan 19, 2009 at 1:52 AM, Héctor López <[email protected]> wrote: > Ok, i'm starting to see some light now. Are you using a custom converter to > create a thing object from an "integer id" or something like that? > > Using your approach, you should code the select with name "thing.id" and the > new object with names "thing.x" and "thing.y". Did another quick test and > again is working ok for me. I'm using this code: No, that will not work. I'm using Stripersist, and the whole point of the selector with the "thing" id is to cause the actual persisted instance to be loaded for the action to use. -- Turtle, turtle, on the ground, Pink and shiny, turn around. ---------------------------------------------------------------------------- -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
