Leif Johansson wrote:
I started playing with the CRUD support in 3.0-SNAPSHOT (HEAD). Great stuff. However shouldn't the <<Identifier>> attribute be treated according to the @andromda.hibernate.generator.class tagged value? The forms generated treat the id attribute as 'assigned' regardless of the generator class. In all cases *except* 'assigned' the CRUD service should ignore (sorta) the value of the id parameter and hibernate do its thing... Right (or am I missing something)?
MVH leifj
Hmm - I guess I *must* have missed something because whatever I stick in the id form field I get 'id must not be null'... Any ideas?
this has been fixed a couple days back, did you try the latest snapshot ?
I still need to update the docs and put the new CRUD sample online, but currently the id is ignored unless it has been explicitely modeled
I will also support the 'assigned' type of identifiers in a later step, the CRUD implementation is very straightforward, if you need a specific feature you might want to take a look at the code (bpm4struts and spring cartridges) and consider creating a patch, should not be too difficult (I'm finishing something at work so I don't have that much free time)
-- Wouter
ps: FYI, just a tip: use <<Unique>> attributes, in a "foreign key" relationship the value of that field will be shown instead of the primary key
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
