On Wed, 2003-10-15 at 19:44, [EMAIL PROTECTED] wrote: > All - am just porting to websphere, and despite my disappointment /w > their db-vendor-specific backends/*xmi files, have found it is not > implemented in xdoclet either. > > Just curious if anyone has used xdoclet successfully /w websphere - can > you confirm that you have to manually maintain the *xmi files using the > websphere tool? Any other pointers for things I will run into - the > current @websphere tags look really slim. (compared to weblogic) > > Has anyone worked on the implementation - and it's just not committed? > > Please confirm if Websphere is a pain in the ass. :(
I confirm Websphere is a pain in the ass. :-) That's nothing to do with the XDoclet module, just recent experience at work. For example, it doesn't work if you have the bean implementation class in a separate package from the home/remote interfaces. And we had all sorts of trouble with it failing to get database connections that turned out to be because we'd (apparently) defined a version 4 datasource, so it couldn't look it up for some reason on our version 5 server. Given that we we did it all through its admin web GUI, you'd think it could have figured it out or warned us or something... As & when I get more familiar with it, you may find the XDoclet support improves :-) In the meantime, if you'd like to help, feel free to upload patches to JIRA. Andrew. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
