Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-582


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-582
    Summary: ejbdoclet attribute to turn on searching for methods in super classes 
(Resubmission of overwritten XDT-547)
       Type: Improvement

     Status: Assigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

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

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Jamie Burns

    Created: Tue, 29 Jul 2003 5:55 AM
    Updated: Tue, 29 Jul 2003 5:55 AM

Description:
This is a resubmission of XDT-547 which was lost over written by a different issue 
during a recent restore from backup. (see 
http://www.mail-archive.com/xdoclet-devel%40lists.sourceforge.net/msg12607.html)

By default ejbdoclet does not seem to look for ejb lifecycle methods in an entity 
beans super class. The problem is related to xjavadoc and is addressed in

http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?id=10100

The solution above has a number of shortcomings.

1. It is difficult to find because it is not documented.
2. Ants command file has to be modified to include 
   -Dxjavadoc.compilemethods=true
(Even though Ant accepts a -Dkey=value argument on the command line it does not place 
the key/value into the system properties.)

My proposed solution to this problem is to add an attribute to the EjbDocletTask which 
sets the system property that xjavadoc is looking for. I have called the attribute 
loadBinaryMethods. The addition of this attribute will address the shortcomings 
mentioned above. I have not been able to attach a recent diff file due to problems 
accessing the CVS repository. I was able to get a diff of the EjbDocletTask.java file 
back in June which is included below. I will upload my copy of EjbDocletTask.java to 
this issue so that someone can diff it if the diff below is too out of date.

Index: EjbDocletTask.java
===================================================================
RCS file: 
/cvsroot/xdoclet/xdoclet/modules/ejb/src/xdoclet/modules/ejb/EjbDocletTask.java,v
retrieving revision 1.10
diff -r1.10 EjbDocletTask.java
32a33,37
>      * See [EMAIL PROTECTED] setLoadBinaryMethods(String) setLoadBinaryMethods}
>      */
>     private String  loadBinaryMethods = "false";
>
>     /**
52a58,67
>      * See [EMAIL PROTECTED] setLoadBinaryMethods(String) setLoadBinaryMethods}
>      *
>      * @return
>      */
>     public String getLoadBinaryMethods()
>     {
>         return loadBinaryMethods;
>     }
>
>     /**
73a89,115
>     }
>
>
>     /**
>      * Controls the depth of searching for methods in binary class sources. When 
> false, xjavadoc will not load methods
>      * and constructor signatures for loaded binary class sources.(A binary class 
> source is a class file rather than a
>      * java file.) This speeds up XDoclet but effectively stops methods in binary 
> class sources being found. If the
>      * presence of a method in a superclass that is presented to XDoclet as a binary 
> source is important set this to
>      * true. This behaviour can also be controlled by the system property 
> <code>xjavadoc.compilemethods</code>. For
>      * example, <pre>
>      *     -Dxjavadoc.compilemethods=true
>      * </pre> has the same effect as <pre>
>      *     setLoadBinaryMethods("true");
>      * </pre>
>      *
>      * @param loadBinaryMethods          String indicating the behaviour when 
> searching for methods in binary class
>      *      sources.
>      * @throws IllegalArgumentException  If <code>loadBinaryMethods</code> is 
> <code>null</code>
>      */
>     public void setLoadBinaryMethods(String loadBinaryMethods)
>     {
>         if (loadBinaryMethods == null)
>             throw new IllegalArgumentException("Cannot set loadBinaryMethods"
>                 + " with a null value");
>
>         System.setProperty("xjavadoc.compilemethods", loadBinaryMethods);
>         this.loadBinaryMethods = loadBinaryMethods;





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



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to