On Sun, 2005-03-13 at 10:40 +1300, Simon Kitching wrote: > On Sat, 2005-03-12 at 18:20 +0000, robert burrell donkin wrote: > > i've been doing some digging today. i've been trying to find a sun > > specification (other than the J2SE javadocs) that mandates the context > > classloader is set appropriately. this is something which J2EE > > containers generally do but i was wondering whether this was actually > > mandated or not. > > > > anyone know? > > I've been doing quite a lot of research into this sort of thing over the > last couple of days. > > The official spec is: > http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf > > Section 6.2.4.8:
thanks interesting :) the reason why i couldn't find it is that this section (and presumably the requirement) was introduced in J2EE 1.3. it isn't present in the J2EE 1.2 specification. this helps to explain some of the odd problems with obscure platforms. (hopefully more on this later) > BTW, sections 8.2 through 8.4 are also relevant to classloading > behaviour of j2ee environments. I'm pretty sure this mandates > child-first classloading (though the specs are just as badly written > here as they are in 6.2.4.8). IIRC earlier specifications were a complete mess when it came to classloading: very little was specified. vendors developed their own preferred classloading models. there were arguments about backwards compatibility on platforms when it comes to mandating default behaviour (as opposed to being able to configure the container). most vendors still encourage users to use their preferred classloader models and most documentation and help is aimed in that direction. see http://www.onjava.com/pub/a/onjava/2001/07/25/ejb.html for history > I'll send a separate email on that topic > soon. great - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
