On 2002.08.16 05:13:25 -0400 Marius Kotsbak wrote: > What will scoped ears be replaced with in jboss 3.2? I heard that > scoping will not be used in 3.2.
Where did you hear this? AFAIK it is a permanent feature. There is no reliable way to load two versions of the same class otherwise. > > We have used it in 3.0 and found some limitations (I can detail this if > it isn't clear). Please detail the problems. If there are bugs, have they been fixed in later versions? Our preferred solution is, I think, to have the > classloader first look in the jar the bean is placed in, and if it > doesn't find it there, look in the global scope, including other > jars/ears. This will solve our problems, and remove the need for scoped > ears. Possibly for your particular application, but not in general. If your app has packages A and B, with classes in A referring to classes in B, and you wish to deploy 2 versions of this app (A1 B1 and A2 B2), with your scheme there is no way to determine if A1 should get classes from B1 or B2. Scoping is required so A1,B1 is invisible to A2,B2 and vice versa david jencks > > -- > Marius Kotsbak > Boost Communications A/S > Trondheim, Norway > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
