There may be others but the one I wrote is org.jboss.test.jmx.test.EarDeploymentUnitTestCase which has an ear with 2 jars, each with one ejb. The ejb-jar.xml in each has a bean using the _other_jars' class. So it shows that _all_ jar classes are availiable before _any_ ejb is created.
david jencks On 2002.02.27 16:13:51 -0500 marc fleury wrote: > Ok just for status do we have a testsuite JUNIT on class visibility? > > If yes sorry and please point me to it, > > if no then I think we should have (please help complete) > > ear > war > war/jar (containing class A, servlet B) > war/webinf/lib/jar (Containing class C taking class A, E) > war/webinf/lib/ (containing class D taking class A, E) > war/webinf/classes/<directory> (containing class E) > many jars (containing class F taking A, E and a duplicate of class A, > calling class G) > a sar inside (containing class G taking F and E) > > Anything else? there are thousand more scenarios but I want to hear from > you > (also be ready to code them when we do the JUNIT crap. > > I am about to embark on client side interceptors and Invocation return > which > shouldn't take me that long (says he as he embarks on a trip to the south > pole and canoe) > > marcf > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
