Julian Gosnell wrote: > So, > > Are you saying that we should simply support both - > but not a third strategy which somehow supports > sandboxing AND optimised intra-container calls ?
Well, I believe the real fix is to make the EJB-loader use the "non Java2" class-loading style as well, i.e. force people to bundle in JAR's that the app is going to use. That is the ultimate way to get things portable, and to be able to allow different running apps use different versions of, say, JAXP. > I think, after a good 5 mins deep consideration, that > the App server should provide the following classes to > a SANDBOXED application. > > 1. J2SE x.x > 2. J2EE y.y > 3. Common local infrastructure What goes into 3? 1 and 2, yes. That must be available from the classloader. > Since the app is sandboxed, it should be able to > override these with it's own version. > > I guess if you want your own version of JAXP then you > should probably have to include your own > implementation as well. Absolutely. And that is indeed the case, or you'll get funky classcast exceptions (we had those a couple of days ago and had muchos fun trying to figure out what happened). > Should the app-server not try, even in this situation, > to optimise intra-container calls ? Well, what is the need to optimize them anymore, really? I mean, use local interfaces and that's it. The proxies don't have to do the check, since it will be implied from what type of proxies that are used. Hey, it's portable too. /Rickard -- Rickard Öberg _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
