Cascading PolicyClassLoaders, is this a wished effect?

[Marcos Sanz/Denic]

Hi all,

as far as I know, the current ClassLoader delegation hierarchy in Phoenix
at the moment should be:

System ClassLoader   <--- Kernel ClassLoader
                     <--- Application 1 ClassLoader
                     <--- Application 2 ClassLoader
                                   [...]

However I am experimenting following behaviour:

System ClassLoader   <--- Kernel ClassLoader
                     <--- Application 1 ClassLoader <--- Application 2
ClassLoader <--- [...]

I cannot figure out what this could be useful for. Moreover, it is breaking
my application. Could somebody ellaborate on that?

Thanks and regards,
Marcos Sanz


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>