Peter
I'll reply to other points more fully in the morning, but for now (given this paragraph is what I think is your central wish)...
Essentially what I want to be able to do is to create a servlet/mailet/whateverlet server that abides by all the rules but does not need to resort to ugly classloader hacks to get working. Not sure - may need more gestation time ;)For the sake of example - can we talk in terms of Jesktop (my bizarre GUI app hoster). Jesktop hosts GUI apps that need Swing, some DesktopKernel access and some "Frimble" access for abstraction of Windowlike containment.
To all intents and purposes, classloaders look like this at present
SysClassLoader <---- Phoenix stuff and Jesktop's jars <--------- BeanShell (hosted app)
|
|----- TextPad
|
|----- SwingSet Demo
Jesktop and Phoenix should have it's kernel operations running in a different *visible* classloader to the hosted applications. Like so:
|----- Jesktop Impl
|
|----- Phoenix Impl + Excalibur etc.
|
SysClassLoader <---- Phoenix & Jesktop API plus nano-Kernel <--------- BeanShell (hosted app)
|
|----- TextPad
|
|----- SwingSet Demo
OK, because at present, Jesktop is hosting applications just *fine*, and security is acheived through proxies and access modifers (not ideal).
Is that what we're talking about?
Regards,
- Paul H
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
