Apply XDoclet to a J2EE project What is XDoclet? • Javadoc metadata templating engine • Attribute-oriented programming • Outgrown its EJBDoclet roots Why XDoclet? • Avoid code metadata duplication • Pragmatic Programming: • DRY - Don’t Repeat Yourself • Program close to the problem domain • Write code that writes code • JSR’s 175 & 181 JSR 175 A metadata facility for the Java Programming Language would allow classes, interfaces, ?elds, and methods to be marked as having particular attributes. JSR 181

This JSR defines an annotated Java format that that uses Java Language Metadata (JSR 175) to enable easy definition of Java Web Services in a J2EE container. • Built upon XJavaDoc XDoclet Architecture • Separated into modules • Embedded templates • Sophisticated Ant tasks with dynamically loaded subtasks • Tag handlers Version 1.2 XJavaDoc • JavaCC-based source code parser • Builds model of: • Packages • Classes / inheritance hierarchy • Methods and parameters • Member variables • Constructors • Custom @tags • … oh yeah, and Javadoc comments too ToDo List Overview Packages org.example.antbook.ant.lucene (4) org.example.antbook.common (1) org.example.antbook.web (1) Todo list for Location org.example.antbook.ant.lucene.Fil eExtensionDocumentHandler Generated by XDoclet. Description Implement dynamic document type lookup Classes IndexTask (1) org.example.antbook.ant.lucene.IndexTask private void indexDocs() org.example.antbook.ant.lucene.TextDocument Fix JavaDoc comments here public java.lang.String getContents() org.example.antbook.common.SearchQueryException Add printStackTrace and other constructors org.example.antbook.web.SearchInitServl et Refactor to use JNDI for directory lookup. finish this method refactor!!!!! SearchInitServlet (1) SearchQueryException (1) TextDocument (2)

Download pdf Introduction to XDoclet