In an effort to fully isolate anything that might be keyed by ContextClassLoader (including FactoryFinder internal state), we created a trivial wrapper ClassLoader to provide a unique ContextClassLoader in setUp() and restore it back to the original in tearDown().
Kind Regards,
John Fallows.
On 2/20/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> The call is required in the setUp() method to make things work correctly on
> the *first* test, when you have the MyFaces implementation in the classpath
> of the tests. Calling it in tearDown() doesn't hurt anything, but protects
> test developers who try to subvert the JUnit test lifecycle stuff.
Exactly. I don't think its necessary in the teardown but it won't
hurt. Its *defnitely* needed in the setup for the reason you
mentioned.
> Craig
Sean
--
http://apress.com/book/bookDisplay.html?bID=10044
Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
