Put your current key fields declaration in the other role, and change 
the current role to an empty key-fields element.  You are thinking the 
old backwards (like the sql references decl).

-dain

Justin Casp wrote:

> Hello list,
> I have a question regarding mapping CMR fields to table columns.  I read about 
> this problem in the JBoss forums, but the solutions I found there don't seem 
> to work with the latest code in CVS.  Specifically, I am trying to use the 
> <key-fields> element which is contained by the <ejb-relationship-role> 
> element as specified in the jbosscmp-jdbc dtd.  The problem is that the 
> container doesn't want to allow this for some reason:
> 
> org.jboss.deployment.DeploymentException: Role: (MyRole) with multiplicity 
> many using foreign-key mapping is not allowed to have key-fields
> 
> for more details, please take a look at this forum post:
> http://main.jboss.org/forums/thread.jsp?forum=46&thread=15444
> 
> Dain mentioned that the directions for this are forthcoming in his new docs.  
> Dain, if you can give me a hint here on how to get past this, I promise I'll 
> still buy the next version of your docs ;)
> 
> Thanks in advance!
> Justin
> 
> PS is there a searchable archive of this list?  I found the geocrawler 
> archive, but I didn't notice a search feature.
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to