--- Julian Gosnell <[EMAIL PROTECTED]> 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 ? > > 1. Serialised. intra-vm calls should cause a > suitable > WARNING - not an ERROR. > > 2. I believe that we need a third strategy. > > This is not the 'ex-cathedra' pronouncement that I > was > hoping someone else would make, I haven't given it > enough thought - but it might be a start. > > 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 > > 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.
Oops - this should read: I guess if you want your own implementation of JAXP, then you should probably have to reinclude the JAXP api itself.... > > Should the app-server not try, even in this > situation, > to optimise intra-container calls ? > > Jules > > --- Rickard Öberg <[EMAIL PROTECTED]> wrote: > > Julian Gosnell wrote: > > > > > Your just putting the onus on the Application > > > programmer to work around shortcomings in the > > Server - > > > I think..... > > > > > > Yes, the app programmer needs to know about > > classloading. Bug.. > > feature.. bug... feature.. which'll it be? :-) > > > > On the one hand, having straight-forward > > classloading makes it easy to > > develop a web-app. On the other hand, having > > sandboxed classloading > > makes the web-app more self-contained and > portable, > > since they don't > > rely on the surrounding server to provide any of > its > > classes. > > > > > If you do that with Jetty in stand-alone, > > compliant > > > mode - you will simply find you are using the > JAXP > > > that Jetty loaded to parse it's own XML > > configuration > > > files. > > > > > > Yes, the straight-forward mode. > > > > > > > If you do it with Jetty in embedded, > non-compliant > > > mode - you will find isAssignableFrom() fails. > > > > > > Yup, the more complex and portable case. > > > > /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 > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Universal Inkjet Refill Kit $29.95 > Refill any ink cartridge for less! > Includes black and color ink. > http://us.click.yahoo.com/1_Y1qC/MkNDAA/ySSFAA/CefplB/TM > ---------------------------------------------------------------------~-> > > For the latest information about Jetty, please see > http://jetty.mortbay. > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > > __________________________________________________ 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
