> Could it be possible that
> EJBContainer#createEJBContainer() is doing something
> insanely stupid like asking its classloader for a
> list of URLs that it should scan? Because of course
> if it does that it won't get the Class-Path: manifest
> entries, will it?
Just hacked the living snot out of the parent URLClassLoader to shove in the actual URLs from the surefire manifest, so that by the time EJBContainer is run it's running with a "real" classpath, just in case that was the issue.
It's not. Of course.
So lessons learned so far:
1. Always specify MODULES. Yes, that means re-creating your classpath.
2. There must not be a TCK entry for this particular specification component. Ahem.
3. "No configuration" NEVER EVER EVER means no configuration.
Plowing ahead to see what else is broken here. :-(
[Message sent by forum member 'ljnelson']
http://forums.java.net/jive/thread.jspa?messageID=395774