XDoclet is used to maintain the many configuration files required by the tools used by GRITS (for example, Hibernate). The use of XDoclet is importnat because it keeps all of the information abount an object (for example, it's database mapping information) in one place where it belongs, namely the Java source file itself. The XDoclet distribution is very modular and has its functionality distributed across several jar files, which allows a project to use only the subset of functionality it needs. we need We currently use XDoclet to generate
Third Party Tool |
Version |
Home Page |
Required |
Included in CVS |
|---|---|---|---|---|
Java 2 Platform, Standard Edition |
1.4.2 |
Yes |
No |
|
Apache Ant |
1.6.1 or later |
Yes |
No |
|
commons-logging |
1.0.3 or later |
Yes |
Yes |
|
log4j |
1.0.3 or later |
Yes |
Yes |
|
commons-lang |
2.0 or later |
Yes |
Yes |
|
XDoclet |
1.2.1 |
Yes |
Yes |
|
Hibernate |
2.1 |
Yes |
Yes |
|
WebWork2 |
2.1 or later |
Yes |
Yes |
|
SiteMesh |
2.0.1 or later |
Yes |
Yes |
|
JUnit |
3.8.1 or later |
No |
Yes |
|
DbUnit |
2.1 or later |
No |
Yes |
|
MockObjects |
0.09 or later |
No |
Yes |
|
displaytag |
1.0-rc1 or later |
Yes |
Yes |
|
JSP Standard Tag Library |
1.0 (not 1.1) |
Yes |
Yes |
|
HSQL Database Engine |
1.7.2 or later |
Yes |
Yes |
|
MySQL JDBC driver |
3.0.12 or later |
Yes |
Yes |
|
Oracle 9i JDBC driver |
9.2.0.3 or later |
Yes |
Yes |