Hi!

I'm playing around with the TCK suite for a few days and almost all tests got 
skipped. I tried this with tomcat and also as standalone, and both give similar 
results.

Let's stick with the standalone container for now:

1.) The webbeans-ejb plugin (which we should rename to webbeans-openejb imho, 
because it uses a lot internal OpenEJB functionality) doesn't get startet up 
correctly. I fixed that part in the PluginLoader and added a starup logic to 
the EJBPlugin. I'm not sure about this part since OpenEJB should already be 
started up, isn't? In the TCK it isn't so I got a NullPointerException because 
SystemInstance.get().getComponent(ContainerSystem.class);
returned null.

We should sum up in which scenarios OpenEJB gets started up at which point in 
time/bootstrapped from which component.

2.) I'm not sure why all the dependencies got copied over with dependency:copy 
instead of simply setting the test dependencies? Imho the only thing we have to 
dependency:copy are those parts which are accessed via a file path instead of 
getting it via the classloader (afaik only the testng-suite.xml)

Oki, that should be it for now ;)

I'll continue to figure out why most of the TCK tests get skipped.

LieGrue,
strub

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com

Reply via email to