> > Yup, agree. In fact a good way of testing the generated code > > is to actually call the code. > > So. > To begin with something simple. > I will check in a junit part so that everybody can add unit tests when > they see something wrong in a generation of samples. > I don't mean calling a jboss/... that run the bean but call the > CMP/Session/... Class directly. > We can even use simple Reflection at the beginning to verify an > interface have a correct definition, throws the correct exceptions, > etc.... > I leave XML to Dmitri. > The things that breaks often is inheritance in Class and deployment > descriptors.
Excellent. We should start somewhere and good ideas will come for sure. > Unit testing Xdoclet classes themselves would be good but later. Yeah, don't invest time on it because using xjavadoc in xdoclet will change everything. The calling sequence is going to change a lot, a new layer comes into existence. > > > > Ara. > > Vincent > "Petit � petit l'oiseau fait son nid" Yup! Petit � petit or in Armenian Kamas Kamas ;-) 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
