> > xjavadoc will be able to do the content comparison. > Will this be easier or harder to set up than comparing classes by > reflection?
No significant difference, they are almost the same but one works on binary the other on code. In fact xjavadoc internally uses reflection to setup the doclet info for a binary class. Problem is xjavadoc is still under development. > You can easily > > compare class/method signatures, but what about actual code? How do you > > check if the body of the generated DO.equals() has the code you're > > expecting?! > I think this is beyond reasonable scope of automated regression testing. > I'd say, write a unit test for the generated class. Yup, agree. In fact a good way of testing the generated code is to actually call the code. Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
