Re: DNA TCK?

Hi,

From: "Leo Simons" <[email protected]>
> I'm even more ambitious: I want to use this stuff to test (most
> importantly, compliance with) potentially all IoC containers in existence
:D

yikes! May be a bit hard with all the different styles. You would just end
up writing a different layer for each different framework. I guess the core
of it would just be recording and playback of invocations. The invocations
could either be incoming (ie the container invoking something on the
component) or outgoing (the component invoking something on one of the
container provided resources).

You may want to check out a few of the mock toolkits as they have that half
done. Though I am not aware of any atm that do this for non-interfaces. I
use jmock.codehaus.org but recently there was a pointer on this list to
http://www.virtualmock.org.

>    http://www.jroller.com/page/lsd/20040114

kool - will have a lookski

> public abstract class AbstractBart extends AbstractComponent
>      public final static Method swear;

ouch!

Go have a play with jmock

> * Using bytecode modification requires control of the classloader (which
> the TCK ideally should not require, as many containers like having that
> control themselves)

Unfortunately I think thats the only way to write a "generic" toolkit. Not
sure though.

> If not, things can still proceed but it's a lot of manual labor :/

yah - thats how most of the jcp TCKs are organized ;(