--- Jim Birchfield <[EMAIL PROTECTED]> wrote: > I just updated and built from CVS and have a problem when I generate > the > Remote interfaces. The imports are not there, so the build fails. > Where'd they go !?!?!?!
Removing the imports were intentional. That's one of the most important changes made recently, so first let's see why I removed them: - Because if I put all imports of impl class in remote/local intf of a bean then that interface has hard dependency to some implementation detail classes. So you won't be able to distribute a jar containing only the interfaces. - This change makes xdoclet less reliant on guesses but rather on explicitly user defined types. We had some bugs where the type was incorrectly guessed or wasn't full qualified at all. - What should xdoclet do if it generates a class which references types imported in a superclass class of a class? Should it also import the imports of the base class? That becomes very tricky and the import list very ugly. Now what you should do is: - make sure you don't get any warning at the end of ejbdoclet. I mean those "the class blabla could not be found, maybe it's generated or not imported, blabla". You can achieve it by either explicitly importing the class (not the package containing the class if it's autogenerated) or defining it fully qualified (com.blabla.Dada). Ara. __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
