You can use a named class loader... So EarA and EarB will not have the same class loaders.. Unless they use the same class loader, which you would have to specify separately, further more you can bring JBoss back to compliance by a setting AFAIK.
2009/9/14 Olivier Bourgeois <olivier.bourgeois....@gmail.com>: > I think you have to put them in different wars and not to use > UnifiedClassloader. The wars have access to the ear classloader (otherwise > they would not have access to the EJBs) so putting 1.2.3 on the ear > classpath and 1.4.x on the war classpath should not work. > > 2009/9/14 nino martinez wael <nino.martinez.w...@gmail.com> > >> I meant ear files >> >> 2009/9/14 nino martinez wael <nino.martinez.w...@gmail.com>: >> > You can if you put them in different wars.. That will work. >> > >> > We have a similar setup that does this. >> > >> > 2009/9/14 Olivier Bourgeois <olivier.bourgeois....@gmail.com>: >> >> Except that you can parameter JBoss to use an "optimization" of its own >> : >> >> UnifiedClassloader : >> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
