You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org> on 2005/05/20 02:17:51 UTC

[jira] Created: (BEEHIVE-752) improve the WSM annotation processor to be more Mirror-like and use less reflection

improve the WSM annotation processor to be more Mirror-like and use less reflection
-----------------------------------------------------------------------------------

         Key: BEEHIVE-752
         URL: http://issues.apache.org/jira/browse/BEEHIVE-752
     Project: Beehive
        Type: Improvement
  Components: Web Services (181)  
    Versions: V1Alpha, V1Beta, V1    
    Reporter: Eddie O'Neil
     Fix For: TBD


The current WSM annotation processor is obviously JDK 5.0 APT based.  In its implementation, though, it uses a cross between reflection and Mirror to do annotation processing.  The result is that with this style project:

  src/
    Service.java
    Account.java

where the WSM annotated web service "Service.java" imports the "Account" class, the .class file must exist on disk in order for the annotations to be processed.  

The result is that WSM projects need to be structured as:

  src/
    Account.java
  src-ws/
    Service.java

so that the src/ directory can be built before src-ws/ to ensure that the .class files for required types are available before annotation processing.

One of the goals of Mirror is to allow annotations in source files to be processed so that the .class files need not exist.  A nice improvement to the WSM annotation processor would be to remove the dependence on reflection and replace it with Mirror-only annotation processing.

We should address this at some point after the next Beehive release...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (BEEHIVE-752) improve the WSM annotation processor to be more Mirror-like and use less reflection

Posted by "Chad Schoettger (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-752?page=all ]

Chad Schoettger updated BEEHIVE-752:
------------------------------------

    Attachment: BEEHIVE-752.txt

Attached patch file for this issue.  Cleaned up to use mirrors instead of classes when processing from apt.

> improve the WSM annotation processor to be more Mirror-like and use less reflection
> -----------------------------------------------------------------------------------
>
>          Key: BEEHIVE-752
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-752
>      Project: Beehive
>         Type: Improvement
>   Components: Web Services (181)
>     Versions: V1, V1Alpha, V1Beta
>     Reporter: Eddie O'Neil
>      Fix For: TBD
>  Attachments: BEEHIVE-752.txt
>
> The current WSM annotation processor is obviously JDK 5.0 APT based.  In its implementation, though, it uses a cross between reflection and Mirror to do annotation processing.  The result is that with this style project:
>   src/
>     Service.java
>     Account.java
> where the WSM annotated web service "Service.java" imports the "Account" class, the .class file must exist on disk in order for the annotations to be processed.  
> The result is that WSM projects need to be structured as:
>   src/
>     Account.java
>   src-ws/
>     Service.java
> so that the src/ directory can be built before src-ws/ to ensure that the .class files for required types are available before annotation processing.
> One of the goals of Mirror is to allow annotations in source files to be processed so that the .class files need not exist.  A nice improvement to the WSM annotation processor would be to remove the dependence on reflection and replace it with Mirror-only annotation processing.
> We should address this at some point after the next Beehive release...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira