Anyway, I thought this would be a good time to start writing test cases for struts-chain stuff. I haven't used MockObjects much, but it seemed like the best way to set up the mock environment. However, when I got down to running the test, I found that the library appears to be hard-coded to throw an AssertionFailedError if you try to retrieve something from the MockServletContext which isn't there.
http://mockobjects.sourceforge.net/javadoc/1.4/com/mockobjects/ReturnObjectBag.html#getNextReturnObject(java.lang.Object)
Does anyone more familiar with MockObjects know if there's a way to turn off this behavior or otherwise specify that it's not an error condition? Obviously in this case I can't write a test case for my fix if I can't simulate the condition where there is not yet any such object in the ServletContext.
I went ahead and committed the fix anyway (rev. 106242) but it would be nice to be able to test it.
I'm going to go ahead and commit the project.xml file that has mockobjects dependencies, since they may still be useful for other tests that we may want to write. This project.xml file also fixes the inheritance from the Struts project.xml file. (For the el libraries, I did this the other way, by copying the files that would otherwise be picked up by inheritance. I'm not sure which I think is more "right" but the inheritance precludes someone from building a source distribution, which is kind of a drag. In this case, it was just faster!)
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
