One-to-many relationship within one bean

Question

hello all,
Does S1 support a container managed one-to-many relationship to itself?
I used the verifer to verify my DD and the error is reported. (this prototype is migrated from weblogic6.1 and I use the S1 migration tool for the DD generation)
-----------------database schema-----------------
CREATE TABLE t_class_a
c_name VARCHAR2(255),
one_class_a_for_ma2918_id VARCHAR2(32), /* untruncated name: one_class_a_for_many_class_a_id */
object_id VARCHAR2(32) NOT NULL
CREATE UNIQUE INDEX t_class_a_id_PK ON t_class_a ( object_id );
ALTER TABLE t_class_a ADD ( CONSTRAINT t_class_a_id_PK PRIMARY KEY ( object_id ) USING INDEX );
ALTER TABLE t_class_a ADD ( CONSTRAINT FK_0 FOREIGN KEY ( one_class_a_for_ma2918_id ) REFERENCES t_class_a ( object_id ) );
---------------------------ejb-jar.xml------------------
<abstract-schema-name>ClassABean</abstract-schema-name>
<cmp-field>
<field-name>objectId</field-name></cmp-field>
<cmp-field>
<field-name>name</field-name></cmp-field>
<primkey-field>objectId</primkey-field>
<relationships>
<ejb-relation>
<ejb-relation-name>manyClassA_oneClassA</ejb-relation-name>
<ejb-relationship-role>
<description>optional</description>
<ejb-relationship-role-name>OneClassA-in-manyClassA_oneClassA</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>ClassAEJB</ejb-name></relationship-role-source>
<cmr-field>
<cmr-field-name>manyClassAsForOneClassA</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type></cmr-field></ejb-relationship-role>
<ejb-relationship-role>
<description>optional</description>
<ejb-relationship-role-name>ManyClassA-in-manyClassA_oneClassA</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>ClassAEJB</ejb-name></relationship-role-source>
<cmr-field>
<cmr-field-name>oneClassAForManyClassA</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
</relationships>
-----------sun-cmp-mapping.xml--------
<sun-cmp-mapping>
<schema>mySchema</schema>
<entity-mapping>
<ejb-name>ClassAEJB</ejb-name>
<table-name>T_CLASS_A</table-name>
<cmp-field-mapping>
<field-name>objectId</field-name>
<column-name>OBJECT_ID</column-name></cmp-field-mapping>
<cmp-field-mapping>
<field-name>name</field-name>
<column-name>C_NAME</column-name></cmp-field-mapping>
<cmr-field-mapping>
<cmr-field-name>manyClassAsForOneClassA</cmr-field-name>
<column-pair>
<column-name>T_CLASS_A.OBJECT_ID</column-name>
<column-name>T_CLASS_A.ONE_CLASS_A_FOR_MA2918_ID</column-name></column-pair></cmr-field-mapping></entity-mapping></sun-cmp-mapping></sun-cmp-mappings>
I beleive the migration tool missing the cmr-filed mapping for the oneClassAForManyClassA relation role.
but even if I add this mapping it still can't pass the verifiy.
So do I miss any thing or I can conclude S1 not support this one-to many self relation?
Any hint would be welcome.

Answer 1

It does.
There is a known problem with parsing self-referenced relationship info - the one side (with <multiplicity> Many) must be the first in the <ejb-relation> entry.
Regards,
Marina