I think that generating test stubs is very subjective - so I'm hesitant to add it to the base of Abator. But Abator is very extensible - you could plug something in that would do what you want.
Also - most IDE's will very quickly generate a stub from an interface - you could use that feature as a starting point and then fill out the specifics as you needed. I am interested in your Spring validator idea. Jeff Butler On 7/6/07, tdev <[EMAIL PROTECTED]> wrote:
the ***DAOStub generation should certainly be made better, e.g.: - instead of the returning 0's defaulting to 1's - a setTestData method to set members, and returning them inside the methods
