Hi, >Options for fixing this are (I haven't look at the code for any of these): >- Do nothing and require the users to restart >- Change the admin app to restart the context after changing the loader >- Modify jasper to check the status of the classloader >- Separate the creating and starting of components through mbeans > >I don't really like any of these options. Does anyone have any better >ideas?
I like #2: in fact, it seems like it should be strictly enforced for general stability and security, and I'm surprised the current code doesn't restart a context after changing its loader already. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
