Hi Thad,
Hmm you're right it does cause an issue like that when you model an relationship like that (because of the create method that takes the required properties and the parentCategory is a required property). Definitely a bug, however I'm not sure the best way to handle occurances like that: what should we do when the create method that takes the required properties only has the a reference to the entity itself as the only required property? I'll have to think about it. To get around it however you should be able to just model an attribute on it that's required as well (I would assume the category would have at least one attribute on it that's required as well?). Can you please file a JIRA issue for this for the Spring Cartridge so I don't forget about it? Thanks. -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1117#1117 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
