i had a similar problem. you may not set cmp fields within
the ejbPostCreate() method. this is an ejb-spec fact. Additionally you may not
set cmr fields within the ejbPostCreate() if they
are container managed. just do not implement the ejbPostCreate. The container (should) do everything
hope this helps,
sven alias wunderkind
Ok thank you!!!
I have not problem with the relationship, i can view and use correctly all public methods of a entity bean from another entity bean without problem.
When i delete the parent entity, the child entity bean is deleted too, because the relation are established in cascade-delete.
The unique problem has when i want to save the child entity, this may save the parent id if all references is ok, or may generate an error if something is bad.
The really complication is that the child entity bean never save the parent id in the child table, i don't know why?
You tell me that the relation is execute automatiquelly for the container, but i think there isn't!!
I think that the major problem now is that the ejbPostCreate() don't execute. Can exist any problem here but i don't know!!!
How i send you my code example for examine ???
are you trying to use a relation table for the relation mapping? This is what you should do in normal case?
> You tell me that the relation is execute automatiquelly
> for the container, but i think there isn't!!
If you are using container managed persistence (cmp)
you really should have found the acronym cmr in the docs.
this means: container managed relationships. no persistence AND no relationship code is needed.