[XDoclet-JIRA] Assigned: (XDT-1453) Value objects don't work on composite with single valued relations

Message:

   The following issue has been re-assigned.

   Assignee: Matthias Germann (mailto:[email protected])
---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1453

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-1453
    Summary: Value objects don't work on composite with single valued relations
       Type: Bug

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: XDoclet
   Versions:
             1.2.3

   Assignee: Matthias Germann
   Reporter: Thomas Winkler

    Created: Thu, 30 Jun 2005 9:57 AM
    Updated: Sun, 14 Aug 2005 3:04 AM

Description:
Value objects don't use the correct method on relations as documented.

The code in the bean is like this:
    /**
     * @ejb.relation 
     *      name="this-that" role-name="this-has-that"
     *      target-cascade-delete="yes"
     *      target-ejb="example.interfaces.ThatEntity"
     *      target-role-name="that-belongsTo-this"
     */
    public abstract example.interfaces.ThatEntity getThatField();
    public abstract void setThatField(example.interfaces.ThatEntity that);

    /**
     * @ejb.value-object 
     *      compose="example.vo.ThatEntityVO" 
     *      compose-name="VOAccessThat"
     *      members="example.interfaces.ThatEntity"
     *      members-name="ThatVO" relation="external"
     * @ejb.interface-method
     */
    public example.interfaces.ThatEntity getThat() {
        return getThatField();
    }

    public void setThat(example.interfaces.ThatEntity that) {
        setThatField(that);
    }



In my opinion the CMP-Class should call the follwing method on the relation:
	relation.setThatVO(valueHolder.getVOAccessThat());

But the name of the compose-name is called instead:
        relation.setVOAccessThat(valueHolder.getVOAccessThat());

This could be fixed by modifying entity-value.xdt at two places, but I don't know, if this is really the result that the fields should create.


---------------------------------------------------------------------
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