Today is still working on WAS5.1 Jaas IPlanet LDAP issues. Since accepting this J2EE application transplant task, I really didn't think that the application ported from JBoss to WebSphere would be so troublesome. The XDoclet generated J2EE configuration failed to adapt to WebSphere, find an XDoclet to support WebSphere's plugin so that EntityBean Implement the CMP configuration (only Top to Down, can not do Meet In Middle, the site that releases this plugin says WebSphere implements the configuration of Meet in middle is very complicated, not easy to use xdoclets, if you want to do this It is best to use WSAD and ask IBM technical support. They also say that there is a special configuration in the EAR exported by WSAD when the Meet In Middle mode is, and the application in WebSphere is not very smooth. It's very bad.
The root knot may be that XDoclet supports WebSphere support. IBM technical support recommends using WSAD to handle this problem. The project coding is basically completed, and the XDoclet generated EAR cannot be further introduced into WSAD. If you reconfigure it with WSAD, it is basically equal to rewrite the code once. Faint ...
The project tells me that the development of Ant XDoclet is best not to apply in WebSphere as an appserver project. Unless the version of WebSphere is transparent to the transparent file or a high person develops a JAR package or Eclipse plugin to support the generation of WebSphere deployment files. PS. XDoclet The plugin address that supports WebSphere 5.x and 6.0 http://www.callista.se/enterprise/downloads/xdoclet/modules/ibm/note: The Module Still Lacks Support for Managing or Mapping for Cmp Entity Beans. This is quite a complex thing to support for WebSphere so for now you need to either to use the default (TOP-DOWN) mapping that happens at deployment time in WebSphere or use WebSphere Studio Application Developer for a more sophisticated oR mapping.