I have not experienced this problem however I have used more tags than you
do when setting up my relations, maybe this will help. See notes below..

-----Original Message-----
From: Paul Michael Reilly [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2003 10:01 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [Xdoclet-user] Probable bug in CMR 1-1 bidirectional Weblogic
support


I believe that an XDoclet (1.2B3) bug exists in the generation of the
Weblogic(7.0/8.1) CMP deployment descriptor for the case of a 1-1
bidirectional cmr field.

However, being a relative newbie to XDoclet and Weblogic, I could be
wrong.  Could easily be pilot error.

In any case, when I modify the following DD snippet manually from

   <weblogic-rdbms-relation>
      <relation-name>AlarmMessageRelation</relation-name>
      <weblogic-relationship-role>

 
<relationship-role-name>Alarm-has-a-Message</relationship-role-name>
         <relationship-role-map>
         <column-map>
            <foreign-key-column>message_id</foreign-key-column>
            <key-column>message_id</key-column>
         </column-map>
         </relationship-role-map>
      </weblogic-relationship-role>
   </weblogic-rdbms-relation>

to 

   <weblogic-rdbms-relation>
      <relation-name>AlarmMessageRelation</relation-name>
      <weblogic-relationship-role>

 
<relationship-role-name>Alarm-has-a-Message</relationship-role-name>
         <relationship-role-map>
         <column-map>
            <foreign-key-column>message_id</foreign-key-column>
            <key-column>message_id</key-column>
         </column-map>
         </relationship-role-map>
      </weblogic-relationship-role>
      <weblogic-relationship-role>

 
<relationship-role-name>Message-has-an-Alarm</relationship-role-name>
         <relationship-role-map>
         <column-map>
            <foreign-key-column>alarm_id</foreign-key-column>
            <key-column>alarm_id</key-column>
         </column-map>
         </relationship-role-map>
      </weblogic-relationship-role>
   </weblogic-rdbms-relation>

the expected behavior from the beans is seen, i.e. the DB shows the
1:1 relationship when viewing both the Alarm and Message tables after
the client code runs.  Without the patch, the alarm_id link in the
Message table does not get set (remains null).

The relevent XDoclet snippets are:

AlarmBean:

    /**
     * Return the Message bean associated with this Alarm.
     *
     * @return the Message bean associated with this Alarm.
     *
     * @ejb.interface-method view-type="local"
     *
     * @ejb.relation
     *     name="AlarmMessageRelation"
     *     role-name="Alarm-has-a-Message"
     *** Added Tags ****
     *  target-role-name="Message-has-an-Alarm"
     *  target-ejb="Message"
     *** End of Added Tags ****
     *
     * @weblogic.column-map
     *     foreign-key-column="message_id"
     *     key-column="message_id"
     */
    public abstract Message getMessage();


MessageBean:

    /**
     * Return the Alarm bean associated with this Message bean.
     *
     * @ejb.interface-method
     *
     * @ejb.transaction type="Required"
     *   
     * @ejb.relation
     *     name="AlarmMessageRelation"
     *     role-name="Message-has-an-Alarm"
     *** Added Tags ****
     *  target-role-name="Alarm-has-a-Message"
     *  target-ejb="Alarm"
     *** End of Added Tags ****
     *
     * @weblogic.column-map
     *     foreign-key-column="alarm_id"
     *     key-column="alarm_id"
     */
    public abstract Alarm getAlarm();


I'm looking for validation or refutation that I have encountered a
bug.  If it is a bug, a workaround would be nice.

Thanks,

-pmr


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
---------------------------------------------------------------------------
This email and any attachments constitute non-public information for use
only by intended recipient(s) and may contain confidential information.  If
you are not an intended recipient, please notify our Information Security
Officer immediately at (941) 906-5844 and permanently delete the original of
this email and any attachments, as well as any copies or printouts thereof.
The unauthorized use, dissemination, distribution or reproduction of this
email and any attachments is prohibited and may be unlawful.


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to