04124: | Jini-Browser.xml in bin directory does not work |
Category: Integration Status: ClosedSeverity: MEDIUM Reported against release: 0.8 Fixed in release: 0.8.2 (Beta Refresh 2)
PROBLEM:The Jini-Browser.xml file in the openwings-0.8\bin directory is a
component descriptor that is intended to allow users to run the jini
browser program. However, it does not work when started in the shell
with a "process -start", or with owrun.
The following error occurs:
java.lang.SecurityException
at
com.mot.openwings.container.jvm.ContainerJVMSecurityManager.checkPermiss
ion(ContainerJVMSecurityManager.java:173)
at java.lang.System.setSecurityManager0(System.java:222)
at java.lang.System.setSecurityManager(System.java:214)
at com.sun.jini.example.browser.Browser.main(Browser.java:1322)
at com.sun.jini.example.browser.Browser.main(Browser.java:1340)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:42)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:28)
at java.lang.reflect.Method.invoke(Method.java:313)
at com.mot.openwings.container.jvm.ProcessMainThread.run
(ContainerJVMProcessThread.java:486)
This ComponentDescriptor should match the version embedded in the
ContainerManagerPolicy.
Verify on a build dated 12/14/01 or later. ANALYSIS:The Jini browser cannot run inside an Openwings container because it
attempts to set a SecurityManager without first checking to see if one
is set. The container SecurityManager disallows the Jini-browser's
request to change the SecurityManager, and the Jini-Browser program
cannot recover from this.
The solution is to run the Jini-browser as a standalone program. WORKAROUND:Edit the Jini-Browser.xml file, and change the value
of "sharedContainerHint" flag to "false".
|