I just verified this fix using Oracle TopLink Essentials - 2.0.1 (Build b03-fcs (10/03/2007). It now seems that unidirectional @OneToMany relations seem to work, but cascaded delete operations on unidirectional @OneToOne relations are still/again broken. The delete order seems to be determined by the alphabetical order of the class names, causing a table constraint violation. Could you check on that?
Regards
Heiko
[Message sent by forum member 'hewagn00' (hewagn00)]
http://forums.java.net/jive/thread.jspa?messageID=238918