Am I right, that for each relation in a generatd CMP class only one set of add-/update-/remove-method is genrated, so it is impossible to have different aggregate-/compose-types for one relation?
For example /** * @ejb.value-object name="OneLightValue" match="light" * @ejb.value-object name="OneNormalValue" match="normal" */ Public abstract class OneBean /** * @ejb.relation ... * @ejb.interface-method * @ejb.value-object * match="light" * compose="ComposeLightValue" * compose-name="Compose" * members="ComposeLightLocal" * members-name="Compose" * type="Collection" * relation="external" * @ejb.value-object * match="normal" * compose="ComposeNormalValue" * compose-name="Compose" * members="ComposeLightLocal" * members-name="Compose" * type="Collection" * relation="external" */ public abstract Collection getComposes(); Will only generate public void addCompose(ComposeLightValue value) ... Public void updateCompose(ComposeLightValue value) ... Public void removeCompose(ComposeLightValue value) ... In the OneCMP.java. Even the getOneNormalValue()-method will not compose the ComposeNormalValue, but the ComposeLightValue. I looked deeply into the latest ValueObjectTagsHandler.java, the corresponding valueobject.xdt and entity-value.xdt, but could not fix it. It seems that the add/update/remove methods are only generated once by "forAllRelations". It should me called something like "forAllRelationsAndValueObjects". And at the other places, it had to be corrected, too. Is there anyone out there, who had the same problem, perhaps an solution? Thomas ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
