jsk-policy.jar file
Once you have unarchived this release, your installation folder should contain most if not all of the following items.
- DISCLAIMER
- The disclaimer regarding the fact that this project is currently under incubation at The Apache Software Foundation.
- LICENSE
- The Apache License.
- NOTICE
- The file containing contributor acknowledgments.
- configentry
- The directory that contains configuration entry description files for all of the River services and utilities
- doc
- The directory that contains specifications, API documentation, manual pages, release notes, license information, and other documentation
- lib
- The directory where the non-download JAR files are located
- lib-dl
- The directory where the download JAR files for the services are located
- lib-ext
- The directory where the dynamic security policy provider is located
- src
- The directory where source code may be located if installed via the separate source release, which is only available as a separate download.
- examples/hello
- The directory where the Hello example is located
jsk-policy.jar file
This release includes a security policy provider which supports dynamic granting of permissions at run-time. Although use of this policy provider is not required, its use is highly recommended when deploying secure applications and services. To permit effective use of this policy provider, it must first be installed as an extension in the Java 2 SDK (or JRE) that you will be using. Note that installing this provider does not automatically cause it to be used, and its installation should not alter the operation of existing applications.
To install this policy provider, providing you didn't do so during your initial installation,
you must copy the jsk-policy.jar file from the lib-ext
subdirectory of your JGDMS release installation to
the extensions directory of your Java(TM) 2 SDK (or JRE) installation.
An alternative to copying jsk-policy.jar to the extension directory is
to use the system property java.ext.dirs. This property specifies one or
more directories to search for extensions, each separated by File.pathSeparatorChar.
To use jsk-policy.jar in this manner, the system property
must be set to include both the path to the Java 2 JRE extension directory
(or directories) and the path to the lib-ext subdirectory of
your JGDMS release installation.
Note that in Java(TM) 2 Standard Edition (J2SE(TM)) 1.4, only the original extension directory
is granted permissions via the system policy file, so you will have to explicitly grant
permissions to jsk-policy.jar in your own policy files. In J2SE 5.0, all the
directories specified in java.ext.dirs are granted permissions so the explicit
permission grant is not needed.
phoenix or rmid
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.