Home

News: JSR 250: Common Annotations for the Java Platform in early draft

  1. JSR-250, a JSR dedicated to creating a set of common annotations for Java, has released an early draft. The specification currently details nine annotations, including:
    • PropertySet, a generalized property set for J2SE
    • Generated, an indicator that the object or class was not hand-written
    • Resource and Resources, annotations to declare single and multiple resource references in J2EE, respectively
    • RunAs, RolesAllowed, Unchecked, and Exclude, annotations to control access to a given method based on J2EE security
    • RolesReferenced, an annotation to specify the roles required by a given class or method
    Of the nine, seven are focused on J2EE.

    Do you have any annotations you'd like to see added to a common repository specification? The JSR is asking for comments, so you should take the opportunity if you're interested.

    See JSR 250: Common Annotations for the Java Platform.

    Threaded Messages (10)

  2. Hani ???????[ Go to top ]

    Has this been this way for a while or is it something new??
    Hani is on the Expert Group for JSR 250 (I guess through his company and not on his own)

    Still, that rocks..
  3. Sounds like XDoclet![ Go to top ]

    Are we recreating XDoclet?
  4. Sounds like XDoclet![ Go to top ]

    Are we recreating XDoclet?

    In a sense, but really we're deprecating XDoclet for a much better solution. Annotations make XDoclet look like child's play. I am anxiously awaiting the day I no longer have to rely on XDoclet and can just use annotations.
  5. Re: Sounds like XDoclet![ Go to top ]

    Are we recreating XDoclet?
    In a sense, but really we're deprecating XDoclet for a much better solution. Annotations make XDoclet look like child's play. I am anxiously awaiting the day I no longer have to rely on XDoclet and can just use annotations.

    I would agree that JDK5 annotations are cool. What I would like to have, though, is a language feature for automatically discovering classes which have a specific annotation type at runtime! For example, I wish Hibernate could ask for all of the classes on the classpath which have an @Entity annotation and automatically include them in the configuration of the SessionFactory. For now, though, I still have to list the specific classes I wish to persist somewhere.
  6. Sounds like XDoclet![ Go to top ]

    Are we recreating XDoclet?

    It would not necessarily be a bad thing to have xdoclet
    as a part of the language, so I personally hope so.

    It would save you from waiting forever between xdoclet
    releases or worse still trying to compile it from source
    or get bugs fixed.

    XDoclet was super cool when it came out but seriously
    that was back in the days when stub generation was something
    you had to do every time you changed a line of code.

    It is starting to show it's age.

    --b
  7. Hani ???????[ Go to top ]

    Talking of membership, my application to join the JSR-250 expert group when it was established (last August or September I think) was rejected.

    Rgds
    Rod
  8. Rod ???????[ Go to top ]

    Talking of membership, my application to join the JSR-250 expert group when it was established (last August or September I think) was rejected.RgdsRod

    And?
  9. Rod's membership[ Go to top ]

    Talking of membership, my application to join the JSR-250 expert group when it was established (last August or September I think) was rejected.
    Rgds
    Rod
    The next time you want to apply tell them you love EJB in non-distributed architectures ;-))
  10. unbelievable[ Go to top ]

    I can't believe that these folks rejected Rod Johnson!

  11. Please can u provide detailed steps to create custom annotations with JSR 250 (javax.annotattions)