--- Rickard Öberg <[EMAIL PROTECTED]> wrote: > 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?
Your site's e.g. Logging classes etc.. which every app uses. You figure it's cheaper to load them once into the apps parent CL, than many times, into every app. > > 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 ? > I'm with you up to here. > 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. > If they are not optimised, RH currently throws an exception and the test fails. So this needs fixing. I have heard of, but know nothing about, local interfaces. I would have thought though, that they must still be constrained by the basic laws of Class "assignability" - i.e. if the way the ClassLoaders is arranged means that instances of a Class cannot be passed directly from one ClassLoader to the other, without serialisation, then your call is going to be slower than if they were. Wether you are using local interfaces or not. Am I wrong ? Anyway, JBoss attempts to implement optimised intra-container calls through the standard interface. Are you suggesting we should throw all this code away now? It would save me a lot of effort. Otherwise this brings us straight back to the same problem. ClassLoader architecture which is what I need to coordinate between JBoss and Jetty in order to pass the testsuite. Jules > /Rickard > > -- > Rickard Öberg > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
