> From: news [mailto:[EMAIL PROTECTED]] On Behalf Of Andrew C. Oliver > > Debugging applications with thick ancestry is a laborious task. But > that gets into Cocoon and Cocoon is in may ways (don't get me wrong I > love Cocoon) the ultimate Avalon Anti-pattern.
On this point we agree. However, sometimes it takes making mistakes to learn better ways of doing things. It also takes a keen eye to determine how to best fix the problem while still providing backwards compatibility. In many ways it can be done, in other ways it requires some things to be changed in backwards incompatible ways. Good tools to help with debugging are proper use of logging, instrumentation, and a good debugger that lets you step through your software. Avalon does have tools to make logging and instrumentation happen, but the debugger is out of its control. Does that mean you have to use Avalon? no. Does it mean that Avalon is the best thing since sliced bread? For many applications I think it is, but there are several applications where it is ill-suited. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
