Support Forums: Message List - New JSR 269: Pluggable Annotation Processing API

hi

Fri, 04 Jan 2013 06:51:18 -0500

yes,,..a video would be perfect for instruction purposes

the stork club movie

API

Fri, 04 Jan 2013 06:39:54 -0500

i was wondring if there is a video on Pluggable Annotation Processing API

buffalo freelance web designer

Java Evolving

Wed, 12 Jul 2006 12:55:40 -0400

So what if Java evolves? I think it is good that Java gains more and powerful features, even if they are borrowed from C++ or C#, as long as it doesn't repeat the mistakes those languages make in designing them....

Ahh, Annotation Based Programming...

Fri, 04 Feb 2005 06:26:21 -0500

The very wide usage of xdoclet shows that there is a true need for meta-data on Java artifacts. You can argue against it on aesthetic or theoretical grounds (e.g. introducing dependencies on your database schema into the Java-code of your persistent...

Ahh, Annotation Based Programming...

Fri, 04 Feb 2005 03:02:00 -0500

Frankly, I find it somewhat shocking that Java evolves more and more into some sort of C++/C# clone. "Annotation processing at compile time" essentially means overblown compiler directives. Yuck. Also very strange that features get added to the...

Ehhhm, okay, well, ahhhh...

Fri, 04 Feb 2005 02:02:37 -0500

Question is if you will be able after such declaration use in e.g. Eclipse getSize() method with autocompletition.

My worries exactly. However, from what I have seen in Eclipse one needs to save a java file before...

not so ditto

Thu, 03 Feb 2005 11:25:43 -0500

So I'm not saying that the goals of this JSR are bad, just that frameworks should only try to pursue compile-time annotation processing as a last resort.

It's worth noting that compile-time annotation processing does not...

not so ditto

Thu, 03 Feb 2005 11:16:36 -0500

IMHO, frameworks should stay away from byte-code manipulation during compiletime if possible. Annotations (as I stated in my article at...

not so ditto

Thu, 03 Feb 2005 10:43:48 -0500

IMHO, frameworks should stay away from byte-code manipulation during compiletime if possible. Annotations (as I stated in my article at ONJava) are...

ditto

Thu, 03 Feb 2005 10:28:45 -0500

Hi BillThat s exactly the kind of limitation I see in APT. But is that worth a whole new JSR just after APT shipped. Can't we simply make APT evolve to support that ?F.e. Apache Beehive is already making extensive use of it and I suspect...

annotation processing, APT and JSR 269

Thu, 03 Feb 2005 09:23:11 -0500

As I see it, APT is not a standard since it was not the product of a JSR but is "just" part of the Sun JDK 5.0. This can also be seen by the fact that to write annotation processors for APT you work with classes below the com.sun.mirror...

New JSR 269: Pluggable Annotation Processing API

Thu, 03 Feb 2005 08:48:59 -0500

I had written an article on using runtime reflection of annotations for handling framework concerns. It uses the example of building validation onto your setters and discusses the future of framework configuration. Also, read some of the comments as...

ditto

Thu, 03 Feb 2005 08:26:29 -0500

Hi Bill

That s exactly the kind of limitation I see in APT. But is that worth a whole new JSR just after APT shipped. Can't we simply make APT evolve to support that ?

F.e. Apache Beehive is already making extensive use of it and I suspect...

ditto

Thu, 03 Feb 2005 08:02:16 -0500

So what ?APT is already deprecated ? What does this JSR 269 brings ? Tighter integration with "javac" (instead of "apt") ? A way to change the class file of the annotated class beeing proceesed ?Alex

Ditto....

limitations?

Thu, 03 Feb 2005 05:26:58 -0500

You can also see this in the JSR 269 :

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

This JSR is...