> -----Original Message----- > From: Christopher Lenz [mailto:[EMAIL PROTECTED] > Sent: 30 November 2003 13:16 > To: Cactus Developers List > Subject: Re: [proposal] Cactus new vision (2) >
[snip] > Further, I am afraid that the framework code common to all of the target > environments might be too thin. Maybe the common core is more of a > *pattern* than something that can effectively put into a API/SPI > framework. [snip] I think this point is really important. Till now Cactus was considered an end framework for writing J2EE unit tests. I'd like to add a new dimension to Cactus: a tool to help build in-container testing solutions. Thus, I view the core fwk to be a set of helper classes to do that. Of course, we'll continue to provide several testing solutions: servlets, filters, jsp/taglibs and other ones. But the end "applications" are the brokers (or whatever we wish to call them). I'm not sure broker is the right word... The fwk is not called directly by the end-users. Any better name? I was thinking about Testlet. Or we could resurrect the Spine/Thorn idea... or? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
