[XDoclet-JIRA] Commented: (XDT-604) sun one ejb module generates wrong unidirectional CMR mappings

The following comment has been added to this issue:

     Author: Markus Bollig
    Created: Sat, 20 Aug 2005 2:37 PM
       Body:
I also experienced the problem using sunone.

It seems that the wrong tag </XDtEjbRel:forAllRelationships> is used to iterate the beans' relations.

This tag always returns all relations used in a jar and not only the one of a bean.

It seems that there is another problem.

Xdoclet only generates the mapping used on one side of an bidirectional relation.





---------------------------------------------------------------------
View this comment:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-604?page=comments#action_17172

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-604

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-604
    Summary: sun one ejb module generates wrong unidirectional CMR mappings 
       Type: Bug

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: XDoclet
 Components: 
             SunONE Module
   Versions:
             1.2 Beta 3

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Simon Mittag

    Created: Thu, 14 Aug 2003 12:17 AM
    Updated: Sat, 20 Aug 2005 2:37 PM
Environment: Sun ONE Application Server 7

Description:
The @sunone.relation tag generates two field mapping entries in sun-cmp-mappings.xml for a unidirectional cmr mapping. This leads to a deployment error. 

When having two CMP Beans A and B where A has an unidirectional cmr mapping to B ("A has a B", the @sunone.relation tag being in A), xdoclet generates the following SUN-CMP-MAPPINGS.XML content:

   <sun-cmp-mapping>
        <entity-mapping>
            <ejb-name>B</ejb-name>
            <table-name>B</table-name>
            <cmr-field-mapping>
                <cmr-field-name>RELATIONVALUE</cmr-field-name>
                <column-pair>
                    <column-name>A.RELATIONVALUE</column-name>
                    <column-name>B.ID</column-name>
                </column-pair>
            </cmr-field-mapping>

        </entity-mapping>

        <entity-mapping>
            <ejb-name>A</ejb-name>
            <table-name>A</table-name>
 
            <cmr-field-mapping>
                <cmr-field-name>RELATIONVALUE</cmr-field-name>
                <column-pair>
                    <column-name>A.RELATIONVALUE</column-name>
                    <column-name>B.ID</column-name>
                </column-pair>
            </cmr-field-mapping>
        </entity-mapping>
    </sun-cmp-mapping>

The <cmr-field-mapping> element is in both beans <entity mapping>. Once deleted from "B" the bean deploys.

Is this a bug related to bidirectional CMR? I didn't dig myself through the Sun spec yet, but I presume the CMR mapping has no business inside the entity mapping "B" here while it's unidirectional?



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf