Two days ago I read in the JBoss CMP docs about that, and now remembered about your
problem. In that Docs it says that the FK column must be nullable in order for JBoss
to work correctly. That's because, as said by redBear15, JBoss first deletes the
parent entity and then makes the cascaded dele
As redBeard15 says, I think the problem you have is that you setted the
"on-delete-cascade" reference on the DB instead of on the CMR definition in
ejb-jar.xml file. If that's your case, you should drop the "on-cascade-delete" rule on
your DB and put the element on the CMR definition.
If that's
I'm only a newbie at writing CMP beans using JBoss, but I think JBoss implements
'cascade deletes' by first removing the 'parent' entity first (e.g., your entity A)
and then
removes all related children (e.g., your entity B).
I suspect that if you had written the DB I/O code yourself, you would
|
| bancoProjeto-projetoConfiguraDados
|
| bancoProjeto
|
BancoProjetoRelationshipRole
| One
|
| bancoProjeto
| BancoProjeto
|
|
| projetoConfiguraDados
| projetoConf
Can you provide the stack trace of this exception, as well as the source code of
ejbRemove of the implied beans and the ejb-jar.xml file, please? That could help...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853017#3853017
Reply to the post :
http://www
Could someone please help me. I really need help on this
Thanks
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853003#3853003
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853003
