Preventing HAJOs

As our development teams begin to adopt the use of annotations within
their Java classes, we would like to prevent the devolution of those
classes into HAJOs (heavily annotated Java objects).  Annotations make
sense in some contexts, but not in all.

 

Does anyone know if a Checkstyle engine running against a Java SE 5.0
class would be capable of determining what annotations have been defined
within that class (whether at the class, method or field level)?

 

If that is possible, we would probably pursue the definition of a custom
check that limits the allowable annotations declared within a Java class
to a configurable white list.

 

Thanks,

Mike

 

Michael V. Spoonauer

Technical Architecture

Architecture and Shared Technology Services

Fidelity | Investment Management Technology

  _____  

Mailzone: 

R22C

Phone: 

617-563-2549

Fax: 

617-850-8168

Pager: 

800-759-8352, PIN 1241370

E-mail: 

[email protected] <mailto:[email protected]>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Checkstyle-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/checkstyle-user