Re: Classpath Ordering: Questions, and possible contrib.

2001-06-24 Thread David Bullock
Thanks everybody for some excellent answers on the classloading topic. The security issues are not something I had considered, in naturally thinking that 'look then delegate' is the logical way to go. On the issue of classpath ordering via my .properties file, I was thinking that it would not

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread Glenn Nielsen
[EMAIL PROTECTED] wrote: > > On Sat, 23 Jun 2001, Glenn Nielsen wrote: > > > > I believe there are important security issues, but I'm sure the spec took > > > this into consideration - so probably I'm wrong ( of course, this will be > > > easy to verify later on, there are quite a few ways someo

RE: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread Ignacio J. Ortega
Hola a Todos,David: Thanks for take a look in this area, is hard to test and has little to nothing review and is plenty of big traps ( as the last found ) .. One of the most hard things that TC33 does is to hide the complexity of JDK11 and 12 compatibility without to much hassle for the poor de

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread cmanolache
On Sat, 23 Jun 2001, Craig R. McClanahan wrote: > Servlet 2.3 PFD2, defines sensitive for the purposes of conformance: J2SE > and servlet API classes. Well, that's not very good if you have a "sensitive" driver ( a native JDBC for friver for example ) or similar. But if this is the definition

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread Craig R. McClanahan
On Sat, 23 Jun 2001 [EMAIL PROTECTED] wrote: > On Sat, 23 Jun 2001, Glenn Nielsen wrote: > > > > I believe there are important security issues, but I'm sure the spec took > > > this into consideration - so probably I'm wrong ( of course, this will be > > > easy to verify later on, there are qu

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread cmanolache
On Sat, 23 Jun 2001, Glenn Nielsen wrote: > > I believe there are important security issues, but I'm sure the spec took > > this into consideration - so probably I'm wrong ( of course, this will be > > easy to verify later on, there are quite a few ways someone could try to > > exploit a reversed

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread Glenn Nielsen
[EMAIL PROTECTED] wrote: > > On Sat, 23 Jun 2001, Craig R. McClanahan wrote: > > > > > A) the hierarchy should go: > > > > > > > >SystemCL > > > > | <-- LAYER 1 > > > > lib/common CL > > > >/ \ <-- LAYER 2 > > > >

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread cmanolache
On Sat, 23 Jun 2001, Craig R. McClanahan wrote: > > > A) the hierarchy should go: > > > > > >SystemCL > > > | <-- LAYER 1 > > > lib/common CL > > >/ \ <-- LAYER 2 > > > lib/container lib/apps CL > > >

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread Craig R. McClanahan
On Sat, 23 Jun 2001 [EMAIL PROTECTED] wrote: > Hi David, > > Thanks for this report, I'm impressed on your deep understanding of the > subject. Class loading is one of the most difficult areas, and until Nacho > implemented most of the new loader scheme we had lots of problems. ( that > happen

Re: Classpath Ordering: Questions, and possible contrib.

2001-06-23 Thread cmanolache
Hi David, Thanks for this report, I'm impressed on your deep understanding of the subject. Class loading is one of the most difficult areas, and until Nacho implemented most of the new loader scheme we had lots of problems. ( that happened few months ago ). > Here's the list of things that I con