Issue 1750: 2 IDL->Java issues on the singleton ORB (02) (java-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: How is an ORB to determine whether or not it is in an applet context? The nearest that I can see is to check for the presence of a SecurityManager. If we are in an applet context, then there is a SecurityManager present, but the inverse (that the presence of a SecurityManager implies that we are in an applet) is not true. It is however the case that whenever a SecurityManager is present, potentially untrusted code is present, so the same constraints on the singleton ORB are probably appropriate. Therefore, I propose that the specification be changed to state that if System.getSecurityManager() returns a non-null result, the singeton ORB should be constrained to creating TypeCodes and Anys. Resolution: Close, no action Revised Text: Actions taken: July 29, 1998: received issue June 4, 1999: closed issue Discussion: End of Annotations:===== Return-Path: Sender: raz@arrakis.com.au Date: Wed, 29 Jul 1998 10:20:40 -0300 From: Roland Turner Organization: - To: java-rtf@omg.org CC: issues@omg.org Subject: 2 IDL->Java issues on the singleton ORB - There may be other work in progress on this, but I just noticed an inconsistency. CORBA 2.2 24.18.8 states variously that, in an applet context, the singleton ORB may only be used for creating TypeCodes and Anys, and later that it may only be used for creating TypeCodes. I assume that the former is correct, perhaps the latter should be amended.