SS,
The attached ReadMe.txt file is distributed with the JRE. I used
it as a guide for what to include.
regards,
Larry
On 6/26/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
Larry,
You highlight some of my ignorance about the way Java programs access
the JRE, and how the JRE is updated.
Would you be able to point out some documentation that discussed the
process, and the advantages, of packaging a JRE with your program?
You may have changed my mind on this, but I would like to do a little
more reading about it.
Thanks,
The Sunburned Surveyor
On 6/26/07, Paul Austin <[EMAIL PROTECTED]> wrote:
> I think there is a case for two installation packages.
>
> 1. Including JVM for the novice Java user
> 2. Without JVM for those who know what they are doing.
>
> Paul
>
> Larry Becker wrote:
> > @SS,
> >
> > Regarding bundling the JRE, I think that there are still some
> > things that are still misunderstood about the seriousness of the
> > issue. Since we started bundling the JRE with SkyJUMP, our install
> > problems have dropped to practically nothing. Before we did, there
> > was a new install problem practically every week. You can run into IT
> > policy issues that don't allow you to install Java at all, or specify
> > a particular version, or don't allow Java updates without
> > coordination. You may find that after you install a new version of
> > Java, that other installed Java programs stop working due to the
> > default JRE changing.
> >
> > I don't understand the reluctance to have multiple copies of the JRE.
> > This is the normal case when you install Java and let Sun install
> > updates, since they never remove old versions for you - in case some
> > program is depending on that particular version of Java. If all
> > reliability and ease of installation costs is hard drive space and
> > download time, I think most users would gladly spend it rather than
> > working for a week getting the program to work.
> >
> > Finally, the bundled JRE is a private copy that is not available to
> > other Java applications. This ensures that updating it will not break
> > any other applications. This allows the latest JRE to be bundled
> > without conflicting with some outdated IT policy that the officially
> > sanctioned version of Java is 1.4 or whatever. These misguided
> > policies were created in the first place because of program
> > dependencies on a single installation of specific version of Java. If
> > every application installed their own JRE, there would be no need for
> > any such policy at all, and most users would be blissfully unaware
> > that they were even running Java the way most windows users are
> > blissfully unaware that their applications built with Windows
> > Foundations Class include a separate copy of most of the WFC dlls.
> >
> > regards,
> > Larry
> >
> >
> > On 6/26/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
> >
> >> Peppe,
> >>
> >> This is great feedback, and I see that Larry and Paul have already
> >> commented. Let me respond to a couple of the things that you
> >> mentioned.
> >>
> >> Peppe wrote: "Setup question.
> >> I started to suggest Openjump to my friends or
> >> students.
> >> The main difficulty I found with people is connected
> >> to Java machine.
> >> Some people do not setup well JAVA machine so
> >> Openjump does't work.
> >> Some other "Windows" people simply don't understand to
> >> "click on Openjum.bat" file to run Openjump. They
> >> expect the launcher on the desktop (and .bat still
> >> remember them the ol'good difficult DOS).
> >> I started to give people a version of Openjump 1.2B
> >> with Java embedded, similar to Openjump Merge.
> >> Proposal: I think it would be fine to have on the web
> >> site two versions of Openjump: a) one with setup and
> >> Java embedded for easy people, b) the second one - no
> >> java no stup - for smart people."
> >>
> >> We definitely need to have an .exe for Windows people. I believe this
> >> can be done with something like JSmooth. We should add it to our to do
> >> list for Windows. Either that or make a shortcut that just executes
> >> the JAR. I don't even think most Windows users would notice it was a
> >> BAT and not an EXE if it had a pretty icon on it. :]
> >>
> >> I don't really like the idea of packaging a virtual machine with
> >> OpenJUMP. For one thing, it makes the download a lot bigger. Also,
> >> what if the user already has a JVM installed? Does he really need two
> >> on his computer?
> >>
> >> I think that a good alternative to this would be some detailed,
> >> step-by-step instructions that explain why a JVM is necessary and how
> >> to install it. Let's not assume all our users are idiots, lets educate
> >> them. :]
> >>
> >> Peppe wrote: "3)DXF/DWG
> >> Openjump is becoming, thanks to edit/drawing tools
> >> and SVG export, a good mapping software. A lot of
> >> mapping datas are in dwg format and some people cried
> >> the absence of a dxf/dwg import option. I always
> >> recomand them the good Michael's dxf plugin.
> >> Proposal: If Michael agrees, this plugin could be
> >> embedded in Openjump.
> >> Regarding dwg I image it is only a problem of time."
> >>
> >> Let me assure you that I believe DXF support is one of the critical
> >> functions for OpenJUMP and that it is in my top 3 list of things to
> >> do. I hope to build on the work of Michael to make a top-notch DXF
> >> import/export plug-in. All, and I mean every last drop, of the
> >> geospatial data used at my office is in some type of CAD format. If I
> >> am ever going to realize my goal of OpenJUMP integration at my job I
> >> have to have killer CAD support.
> >>
> >> On a related note I wouldn't hold my breath for great DWG support.
> >> There are a couple of reasons for this. DWG is a closed format for one
> >> thing. The Open Design Alliance used to publish a spec for the format,
> >> but they just lost some legal battles in the United States and our now
> >> prohibited from doing this. The only way I see us getting DWG support
> >> is if Autodesk publishes the DWG spec or offers some type of free Java
> >> DWG access library. (When I get done with my DXF plug-in you won't
> >> need DWG anyways.) :]
> >>
> >> Remember that DXF is the format Autodesk want's everyone to use to
> >> transfer CAD data. DWG is their money making baby.
> >>
> >> Peppe wrote: "6)Editing tools (not very seriuos!)
> >> It would be nice to have some editing tools in a
> >> "Inkscape-like" style.
> >> Examples, tranfering some editing tools on the mouse:
> >> a) one left-click mouse>edit/move object
> >> b) two left click mouse>edit/move verticles
> >> c) three left-click mouse>free rotation
> >> This probabiy makes Openjump editing tools more
> >> "international-ized"
> >> Is this something difficuld to build?"
> >>
> >> I've done a little bit of work towards this area. I'm in the middle of
> >> replumbing the CursorTool code. I hope to add some support for CAD
> >> like snapping, which should provide some improved editing
> >> capabilities.
> >>
> >> The Sunburned Surveyor
> >>
> >>
> >>
> >> On 6/26/07, Larry Becker <[EMAIL PROTECTED]> wrote:
> >>
> >>> Hi Peppe,
> >>>
> >>> Thanks for your input. We don't get enough of the user perspective
> >>> on the list.
> >>>
> >>> Regarding transferring styles, I would point out the very useful
> >>> copy style and paste style functions in OpenJump. Also, in addition
> >>> to Paul's efforts, I will be porting over SkyJUMP's Merge Task
> >>> function which lets you create new tasks from old ones.
> >>>
> >>> I have also found that Java is the main setup problem for new users.
> >>> I believe it is necessary to bundle the Java Runtime Environment, and
> >>> to include a windows executable.
> >>>
> >>> regards,
> >>> Larry
> >>>
> >>> On 6/26/07, Paul Austin <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> I'm currently working on a whole bunch of enhancements to the styling,
> >>>> specifically around the concept of Theming layers by multiple attribute
> >>>> values. Part of this is a framework to be able to define the filters to
> >>>> select features to match.
> >>>>
> >>>> As part of this I have implemented a very simple way of loading a saved
> >>>> style definition from a Tab Separated file with the style rules. I plan
> >>>> to extend this to allow more "standard" approaches to style definitions
> >>>> such as SLD, when I get to that point we can then create the save/load
> >>>> style from file functionality.
> >>>>
> >>>> I'm just working on the UI aspects of defining the styles, hopefully
> >>>> I'll have something to share soon,
> >>>> Paul
> >>>>
> >>>> Giuseppe Aruta wrote:
> >>>>
> >>>>> Dear Developers
> >>>>> After using Openjump for a while I wrote some
> >>>>> observations and ideas that I had (as user, not as
> >>>>> developer).
> >>>>> I do not want to open a discussion, and probabily some
> >>>>> of these points have no "common feeling" or probabily
> >>>>> always had answer.
> >>>>> I want only to share with you my experience as
> >>>>> newcomer in Openjump, and also the feeling I had from
> >>>>> other people I bring to Openjump
> >>>>> I write them in order of importance (my personal
> >>>>> point of view, of coarse!)
> >>>>>
> >>>>> 1) Export display parameters of a layer to other
> >>>>> projects.
> >>>>> The displayed parameters of a dataset (colours of
> >>>>> lines, polygons, fill, winth, etc) are saved only in
> >>>>> the program file (.JMP). Neverthess, if people want to
> >>>>> use the same dataset in a different project, they must
> >>>>> setup again the displayes parameters.
> >>>>> At the beginning I thought that "View>Tranform layer
> >>>>> Style into SLID" was the function to use. I had to
> >>>>> change my idea.
> >>>>> A function in Openjump that saves displayed
> >>>>> parameters of a dataset to, for example, a sepatate
> >>>>> extra XML or TXT file, would be fine. This file wuold
> >>>>> be used to display again the same parameters when the
> >>>>> dataset is opened again in other projects
> >>>>> I have no idea about the difficulties for developers
> >>>>> to build this function.
> >>>>> The proposal is to have two extra functions on Layer
> >>>>> Menu: "Save Layer Properties to (?) file" and a "Load
> >>>>> Layer Properties from (?) file".
> >>>>>
> >>>>> 2) Setup question.
> >>>>> I started to suggest Openjump to my friends or
> >>>>> students.
> >>>>> The main difficulty I found with people is connected
> >>>>> to Java machine.
> >>>>> Some people do not setup well JAVA machine so
> >>>>> Openjump does't work.
> >>>>> Some other "Windows" people simply don't understand to
> >>>>> "click on Openjum.bat" file to run Openjump. They
> >>>>> expect the launcher on the desktop (and .bat still
> >>>>> remember them the ol'good difficult DOS).
> >>>>> I started to give people a version of Openjump 1.2B
> >>>>> with Java embedded, similar to Openjump Merge.
> >>>>> Proposal: I think it would be fine to have on the web
> >>>>> site two versions of Openjump: a) one with setup and
> >>>>> Java embedded for easy people, b) the second one - no
> >>>>> java no stup - for smart people.
> >>>>>
> >>>>> 3)DXF/DWG
> >>>>> Openjump is becoming, thanks to edit/drawing tools
> >>>>> and SVG export, a good mapping software. A lot of
> >>>>> mapping datas are in dwg format and some people cried
> >>>>> the absence of a dxf/dwg import option. I always
> >>>>> recomand them the good Michael's dxf plugin.
> >>>>> Proposal: If Michael agrees, this plugin could be
> >>>>> embedded in Openjump.
> >>>>> Regarding dwg I image it is only a problem of time.
> >>>>>
> >>>>> 4) Save file observation.
> >>>>> There is still some confusion for newcomers about the
> >>>>> difference betwee "Save Datasets as file..." and "Save
> >>>>> dataset as..". (See Michael and Uwe discussion in
> >>>>> [JPP-Devel] Load/Save dataset design).
> >>>>> I tried to point out in a help documentation I posted
> >>>>> some weeks ago. Nevertheless there are still newcomers
> >>>>> who use "Save dataset as.." ... and they forget the
> >>>>> suffix! I belive, like Uwe, that it is important to
> >>>>> have a suffix built automatically.
> >>>>>
> >>>>> 5) PostGIS
> >>>>> I think it's time to transalte Uwe's Portgis tutorial
> >>>>> in English (if Uwe agrees, of coarse) maybe integrated
> >>>>> with how to use Orbiscad and Openjump together.
> >>>>> Proposal: Does somebody thranslate from German to
> >>>>> English (otherwise this summer I will try to refresh
> >>>>> my scarse German with Uwe's documentation)?
> >>>>>
> >>>>> 6)Editing tools (not very seriuos!)
> >>>>> It would be nice to have some editing tools in a
> >>>>> "Inkscape-like" style.
> >>>>> Examples, tranfering some editing tools on the mouse:
> >>>>> a) one left-click mouse>edit/move object
> >>>>> b) two left click mouse>edit/move verticles
> >>>>> c) three left-click mouse>free rotation
> >>>>> This probabiy makes Openjump editing tools more
> >>>>> "international-ized"
> >>>>> Is this something difficuld to build?
> >>>>>
> >>>>>
> >>>>> Thanks for your attention
> >>>>>
> >>>>> Peppe
> >>>>>
> >>>>>
> >>>>>
> >>>>> ___________________________________
> >>>>> L'email della prossima generazione? Puoi averla con la nuova Yahoo!
Mail: http://it.docs.yahoo.com/nowyoucan.html
> >>>>>
> >>>>>
-------------------------------------------------------------------------
> >>>>> This SF.net email is sponsored by DB2 Express
> >>>>> Download DB2 Express C - the FREE version of DB2 express and take
> >>>>> control of your XML. No limits. Just data. Click to get it now.
> >>>>> http://sourceforge.net/powerbar/db2/
> >>>>> _______________________________________________
> >>>>> Jump-pilot-devel mailing list
> >>>>> Jump-pilot-devel@lists.sourceforge.net
> >>>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>>>
> >>>>>
> >>>> -------------------------------------------------------------------------
> >>>> This SF.net email is sponsored by DB2 Express
> >>>> Download DB2 Express C - the FREE version of DB2 express and take
> >>>> control of your XML. No limits. Just data. Click to get it now.
> >>>> http://sourceforge.net/powerbar/db2/
> >>>> _______________________________________________
> >>>> Jump-pilot-devel mailing list
> >>>> Jump-pilot-devel@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>>
> >>>>
> >>> --
> >>> http://amusingprogrammer.blogspot.com/
> >>>
> >>> -------------------------------------------------------------------------
> >>> This SF.net email is sponsored by DB2 Express
> >>> Download DB2 Express C - the FREE version of DB2 express and take
> >>> control of your XML. No limits. Just data. Click to get it now.
> >>> http://sourceforge.net/powerbar/db2/
> >>> _______________________________________________
> >>> Jump-pilot-devel mailing list
> >>> Jump-pilot-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>
> >>>
> >> -------------------------------------------------------------------------
> >> This SF.net email is sponsored by DB2 Express
> >> Download DB2 Express C - the FREE version of DB2 express and take
> >> control of your XML. No limits. Just data. Click to get it now.
> >> http://sourceforge.net/powerbar/db2/
> >> _______________________________________________
> >> Jump-pilot-devel mailing list
> >> Jump-pilot-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>
> >>
> >
> >
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
--
http://amusingprogrammer.blogspot.com/
README
Java(TM) Platform, Standard Edition
Runtime Environment
Version 6
The Java(TM) Platform, Standard Edition Runtime Environment (JRE) is
intended for software developers and vendors to redistribute with
their applications.
The Java SE Runtime Environment contains the Java virtual machine,
runtime class libraries, and Java application launcher that are
necessary to run programs written in the Java programming language.
It is not a development environment and does not contain development
tools such as compilers or debuggers. For development tools, see the
Java SE Development Kit (JDK(TM)).
=======================================================================
Deploying Applications with the Java SE Runtime Environment
=======================================================================
When you deploy an application written in the Java programming
language, your software bundle will probably consist of the following
parts:
Your own class, resource, and data files.
A runtime environment.
An installation procedure or program.
You already have the first part, of course. The remainder of this
document covers the other two parts. See also the Notes for Developers
page on the Java Software website:
http://java.sun.com/javase/6/webnotes/runtime.html
-----------------------------------------------------------------------
Runtime Environment
-----------------------------------------------------------------------
To run your application, a user needs the Java SE Runtime Environment,
which is freely available from Sun. Or, you can redistribute the
Java SE Runtime Environment for free with your application, according
to the terms of the Runtime Environment's license.
The final step in the deployment process occurs when the software is
installed on an individual user's system. Installation consists of copying
software onto the user's system, then configuring the user's system
to support that software. You should ensure that your installation
procedure does not overwrite existing JRE installations, as they may
be required by other applications.
=======================================================================
Redistribution of the Java SE Runtime Environment (JRE)
=======================================================================
--------------------------------------------------------
NOTE - The license for this software does not allow the
redistribution of beta and other pre-release versions.
--------------------------------------------------------
Subject to the terms and conditions of the Software License
Agreement and the obligations, restrictions, and exceptions set
forth below, You may reproduce and distribute the Software (and
also portions of Software identified below as Redistributable),
provided that:
(a) you distribute the Software complete and unmodified and only
bundled as part of your applets and applications ("Programs"),
(b) your Programs add significant and primary functionality to the
Software,
(c) your Programs are only intended to run on Java-enabled general
purpose desktop computers and servers,
(d) you distribute Software for the sole purpose of running your
Programs,
(e) you do not distribute additional software intended to replace
any component(s) of the Software,
(f) you do not remove or alter any proprietary legends or notices
contained in or on the Software,
(g) you only distribute the Software subject to a license agreement
that protects Sun's interests consistent with the terms
contained in this Agreement, and
(h) you agree to defend and indemnify Sun and its licensors from
and against any damages, costs, liabilities, settlement amounts
and/or expenses (including attorneys' fees) incurred in
connection with any claim, lawsuit or action by any third party
that arises or results from the use or distribution of any and
all Programs and/or Software.
The term "vendors" used here refers to licensees, developers, and
independent software vendors (ISVs) who license and distribute the
Java SE Runtime Environment with their programs.
Vendors must follow the terms of the Java SE Runtime Environment Binary
Code License agreement.
-----------------------------------------------------------------------
Required vs. Optional Files
-----------------------------------------------------------------------
The files that make up the Java SE Runtime Environment are divided into
two categories: required and optional. Optional files may be excluded
from redistributions of the Java SE Runtime Environment at the
vendor's discretion.
The following section contains a list of the files and directories that
may optionally be omitted from redistributions with the Java SE Runtime
Environment. All files not in these lists of optional files must be
included in redistributions of the runtime environment.
-----------------------------------------------------------------------
Optional Files and Directories
-----------------------------------------------------------------------
The following files may be optionally excluded from redistributions.
These files are located in the jre1.6.0_<version> directory, where
<version> is the update version number. Solaris and Linux filenames
and separators are shown. Windows executables have the ".exe" suffix.
Corresponding files with _g in the name can also be excluded.
The corresponding man pages should be excluded for any excluded
executables (with paths listed below beginning with bin/ ,
for the Solaris(TM) Operating System and Linux).
lib/charsets.jar
Character conversion classes
lib/ext/
sunjce_provider.jar - the SunJCE provider for Java
Cryptography APIs
localedata.jar - contains many of the resources
needed for non US English locales
ldapsec.jar - contains security features supported
by the LDAP service provider
dnsns.jar - for the InetAddress wrapper of JNDI DNS provider
bin/rmid
Java RMI Activation System Daemon
bin/rmiregistry
Java Remote Object Registry
obin/tnameserv
Java IDL Name Server
bin/keytool
Key and Certificate Management Tool
bin/kinit
Used to obtain and cache Kerberos ticket-granting tickets
bin/klist
Kerberos display entries in credentials cache and keytab
bin/ktab
Kerberos key table manager
bin/policytool
Policy File Creation and Management Tool
bin/orbd
Object Request Broker Daemon
bin/servertool
Java IDL Server Tool
bin/javaws, lib/javaws/ and lib/javaws.jar
Java Web Start
When redistributing the JRE on Microsoft Windows as a private
application runtime (not accessible by other applications)
with a custom launcher, the following files are also
optional. These are libraries and executables that are used
for Java support in Internet Explorer and Mozilla family browsers;
these files are not needed in a private JRE redistribution.
bin\java.exe
bin\javaw.exe
bin\javaws.exe
bin\javacpl.exe
bin\jucheck.exe
bin\jusched.exe
bin\wsdetect.dll
bin\NPJPI*.dll (The filename changes in every release)
bin\NPJava11.dll
bin\NPJava12.dll
bin\NPJava13.dll
bin\NPJava14.dll
bin\NPJava32.dll
bin\NPOJI610.dll
bin\RegUtils.dll
bin\axbridge.dll
bin\deploy.dll
bin\jpicom.dll
bin\javacpl.cpl
bin\jpiexp.dll
bin\jpinscp.dll
bin\jpioji.dll
bin\jpishare.dll
lib\deploy.jar
lib\plugin.jar
lib\javaws.jar
lib\javaws\messages.properties
lib\javaws\messages_de.properties
lib\javaws\messages_es.properties
lib\javaws\messages_fr.properties
lib\javaws\messages_it.properties
lib\javaws\messages_ja.properties
lib\javaws\messages_ko.properties
lib\javaws\messages_sv.properties
lib\javaws\messages_zh_CN.properties
lib\javaws\messages_zh_HK.properties
lib\javaws\messages_zh_TW.properties
lib\javaws\miniSplash.jpg
-----------------------------------------------------------------------
Redistributable JDK(TM) Files
-----------------------------------------------------------------------
The limited set of files from the Java SE Development Kit (JDK)
listed below may be included in vendor redistributions of the Java SE
Runtime Environment. All paths are relative to the top-level
directory of the JDK. The corresponding man pages should be included for
any included executables (with paths listed below beginning with bin/ ,
for the Solaris(TM) Operating System and Linux).
jre/lib/cmm/PYCC.pf
Color profile. This file is required only if one wishes to
convert between the PYCC color space and another color space.
All .ttf font files in the jre/lib/fonts directory.
Note that the LucidaSansRegular.ttf font is already contained
in the Java SE Runtime Environment, so there is no need to
bring that file over from the JDK.
jre/lib/audio/soundbank.gm
This MIDI soundbank is present in the JDK, but it has
been removed from the Java SE Runtime Environment in order to
reduce the size of the Runtime Environment's download bundle.
However, a soundbank file is necessary for MIDI playback, and
therefore the JDK's soundbank.gm file may be included in
redistributions of the Runtime Environment at the vendor's
discretion. Several versions of enhanced MIDI soundbanks are
available from the Java Sound web site:
http://java.sun.com/products/java-media/sound/
These alternative soundbanks may be included in redistributions
of the Java SE Runtime Environment.
The javac bytecode compiler, consisting of the following files:
bin/javac [Solaris(TM) Operating System
and Linux]
bin/sparcv9/javac [Solaris Operating System
(SPARC(R) Platform Edition)]
bin/amd64/javac [Solaris Operating System (AMD)]
bin/javac.exe [Microsoft Windows]
lib/tools.jar [All platforms]
The Annotation Processing Tool, consisting of the following files:
bin/apt [Solaris(TM) Operating System
and Linux]
bin/sparcv9/apt [Solaris Operating System
(SPARC(R) Platform Edition)]
bin/amd64/apt [Solaris Operating System (AMD)]
bin/apt.exe [Microsoft Windows]
lib/jconsole.jar
The Jconsole application.
jre\bin\server\
On Microsoft Windows platforms, the JDK includes both
the Java HotSpot(TM) Server VM and Java HotSpot Client VM.
However, the Java SE Runtime Environment for Microsoft Windows
platforms includes only the Java HotSpot Client VM. Those wishing
to use the Java HotSpot Server VM with the Java SE Runtime
Environment may copy the JDK's jre\bin\server folder to a
bin\server directory in the Java SE Runtime Environment. Software
vendors may redistribute the Java HotSpot Server VM with their
redistributions of the Java SE Runtime Environment.
-----------------------------------------------------------------------
Unlimited Strength Java Cryptography Extension
-----------------------------------------------------------------------
Due to import control restrictions for some countries, the Java
Cryptography Extension (JCE) policy files shipped with the Java SE
Development Kit and the Java SE Runtime Environment allow strong but
limited cryptography to be used. These files are located at
<java-home>/lib/security/local_policy.jar
<java-home>/lib/security/US_export_policy.jar
where <java-home> is the jre directory of the JDK or the
top-level directory of the Java SE Runtime Environment.
An unlimited strength version of these files indicating no restrictions
on cryptographic strengths is available on the JDK web site for
those living in eligible countries. Those living in eligible countries
may download the unlimited strength version and replace the strong
cryptography jar files with the unlimited strength files.
-----------------------------------------------------------------------
The cacerts Certificates File
-----------------------------------------------------------------------
Root CA certificates may be added to or removed from the Java SE
certificate file located at
<java-home>/lib/security/cacerts
For more information, see The cacerts Certificates File section
in the keytool documentation at:
http://java.sun.com/javase/6/docs/tooldocs/solaris/keytool.html#cacerts
=======================================================================
Endorsed Standards Override Mechanism
=======================================================================
From time to time it is necessary to update the Java platform in order
to incorporate newer versions of standards that are created outside of
the Java Community Process(SM) (JCP(SM) http://www.jcp.org/) (Endorsed
Standards), or in order to update the version of a technology included
in the platform to correspond to a later standalone version of that
technology (Standalone Technologies).
The Endorsed Standards Override Mechanism provides a means whereby
later versions of classes and interfaces that implement Endorsed
Standards or Standalone Technologies may be incorporated into the Java
Platform.
For more information on the Endorsed Standards Override Mechanism,
including the list of platform packages that it may be used to
override, see
http://java.sun.com/javase/6/docs/technotes/guides/standards/
-----------------------------------------------------------------------
The Java(TM) Runtime Environment (JRE) is a product of
Sun Microsystems(TM), Inc.
Copyright © 2007 Sun Microsystems, Inc.
4150 Network Circle, Santa Clara, California 95054, U.S.A.
All rights reserved.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
