> I see. I wasn't sure, since the hasMethod tag doesn't appear to be > included > in the generated template tags documentation.
Oops. I will pay attention to that doco in the future. > >ps : if the name of the method is not speaking, feel free to rename > it > > Probably a good idea, it's a bit confusing at the moment. I take it > the > current method gets reset to the original method when it reaches the > closing > tag i.e. only the tag body gets executed in the context of the > partular > method that was specified? Yes. > In which case, how about "forMethod"? > (it's > similar to forAllMethods, but does it for only the one that's > specified > rather than for each of them...) ... and have 2 forMethod loops, one for the getters and one for the setters ? I think it is better that both are generated inside a unique loop : the "entity bean attributes loop". > > Also, what happens if the bean class only defines a setter for a > field and > not a getter? Not very likely, I know, but possible e.g. for a > password > field. Perhaps the getterMethod bits should also have an ifHasMethod > around > them too? Can you do that in cmp 2.0 abstract classes ? If yes then I guess xdoclet need it too, don't see how right now... > Andrew. Vincent __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
