From: Scott M S. <st...@us...> - 2002-02-19 20:00:18
|
User: starksm Date: 02/02/19 12:00:17 Modified: src/main/org/jboss/test/jbossmx/implementation/server ContextCLTestCase.java Log: Change the comment to refer to Bug#516649 as this is the sar/ejb-jar issue that Bug#519699 was created for. Revision Changes Path 1.3 +2 -2 jbosstest/src/main/org/jboss/test/jbossmx/implementation/server/ContextCLTestCase.java Index: ContextCLTestCase.java =================================================================== RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/jbossmx/implementation/server/ContextCLTestCase.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ContextCLTestCase.java 19 Feb 2002 19:45:03 -0000 1.2 +++ ContextCLTestCase.java 19 Feb 2002 20:00:17 -0000 1.3 @@ -35,14 +35,14 @@ import org.jboss.test.jbossmx.implementation.server.support.ContextCL; /** Test of the mbean operation invocation thread context class loader. This - *test case simulates the problem originally seen in Bug#519699. Reproducing the + *test case simulates the problem originally seen in Bug#516649. Reproducing the *steps here requires a number of contrived steps including simulated reloading *of the mbean from different jars and the loading of the TestData class by *the main MBeanClassLoader using Class.forName(). These are the actions that *occur when reloading a sar that contains an ejb-jar. * * @author Sco...@jb... - * @version $Revision: 1.2 $ + * @version $Revision: 1.3 $ */ public class ContextCLTestCase extends TestCase { |