David Nielsen <mailto:[EMAIL PROTECTED]> once said: > /** > * @ejb:interface-method > * @ejb:relation > * name="MailMessages-toUser" > * role-name="MailMessages-Has-toToUser" > * target-ejb="Users" > * target-role-name="toUser-belongs_to-MailMessages" > * target-cascade-delete="yes" > * @jboss:target-relation > * related-pk-field="messageKey" > * fk-column="messageKey" > * @jboss:relation-table > * table-name="MailMessages_toUsers" > * create-table="true" > * remove-table="true" > ... > jboss creates the mailmessages + the users table but no > mailmessages_tousers table, and there now are a column (messagekey) > in users table.
I haven't used N:M relations without modeling the relation table as a bean itself, but I have a guess anyway. :) Since you're using a unidirectional relation, don't you need to specify * @ejb:relation * ... * target-multiple="yes" ? All of my unidirectional relations have four target-xxx tags. It sounds like JBoss is trying to make it a 1:N relation. David Harkness Sr. Software Engineer Sony Pictures Digital Networks (310) 482-4756 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
