The following comment has been added to this issue:

     Author: Lennart Petersson
    Created: Fri, 17 Dec 2004 2:59 AM
       Body:
This is still a question i have on the current 1.2.2 version.

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

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-522
    Summary: Incorrect behavior when having overloaded methods in CMP 1.1
       Type: Bug

     Status: Open
   Priority: Major

 Original Estimate: 0 minutes
 Time Spent: Unknown
  Remaining: 0 minutes

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

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Lennart Petersson

    Created: Thu, 12 Jun 2003 2:12 AM
    Updated: Fri, 17 Dec 2004 2:59 AM
Environment: Mac OS X Java 1.4.1 CMP 1.1

Description:
Having an CMP 1.1 entity bean with persistent field status. Has following 
getters/setters:

public abstract Integer getStatus();
public abstract void setStatus(Integer status);

And also a non-abstract setter with other parameters and with an exception:
public void setStatus(Integer status, boolean something) throws MyException
{
   try
   {
      bla bla bla
      setStatus(status);
   }catch(Exception e){throw new MyException(...);}
}

2 problems when generating MyClassCMP.java:

1) getStatus and setStatus in the MyClassCMP.java will have incorrect 
super-call to the abstract method in the MyClassBean.java. Temporarly resolved 
by removing isAbstract-tests in entity-cmp11.xdt

2) setStatus in MyClassCMP.java will have the exceptionlist from the 
setStatus(Integer, boolean) method in MyClassBean.java. Looks like method 
AbstractProgramElementTagsHandler.exceptionList ignores the fact that there 
might be overloaded methods when entering this line of code:
            executableMember = getXExecutableMemberForMemberName(memberName, 
true, forType);
where memberName will be "setStatus". Shouldnt there be a parameterlist also to 
qualifiing the correct method to use!?

/L



---------------------------------------------------------------------
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 email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to