Skip to main content

JDK and JRE File Structure

Assuming the JDK software is installed at c:\jdk1.7.0, here are some of the most important directories:

c:\jdk1.7.0

Root directory of the JDK software installation. Contains copyright, license, and README files. Also contains src.zip, the archive of source code for the Java platform.

c:\jdk1.7.0\bin

Executable files for the development tools contained in the Java Development Kit. The PATH environment variable should contain an entry for this directory. For more information on the tools, see the JDK Tools.

c:\jdk1.7.0\lib

Files used by the development tools. These include tools.jar, which contains non-core classes for support of the tools and utilities in the JDK. Also includes dt.jar, the DesignTime archive of BeanInfo files that tell interactive development environments (IDE's) how to display the Java components and how to let the developer customize them for an application.

c:\jdk1.7.0\jre

Root directory of the Java runtime environment used by the JDK development tools. The runtime environment is an implementation of the Java platform. This is the directory represented by the java.home system property.

c:\jdk1.7.0\jre\bin

Executable files and DLLs for tools and libraries used by the Java platform. The executable files are identical to files in /jdk1.7.0/bin. The java launcher tool serves as an application launcher (and replaced the old jretool that shipped with 1.1 versions of the JDK). This directory does not need to be in the PATH environment variable.

c:\jdk1.7.0\jre\bin\client

Contains the DLL files used by the Java HotSpot™ Client Virtual Machine.

c:\jdk1.7.0\jre\bin\server

Contains the DLL files used by the Java HotSpot™ Server Virtual Machine.

c:\jdk1.7.0\jre\lib

Code libraries, property settings, and resource files used by the Java runtime environment. For example:

c:\jdk1.7.0\jre\lib\ext

Default installation directory for Extensions to the Java platform.

  • localedata.jar -- locale data for java.text and java.util.

c:\jdk1.7.0\jre\lib\security

Contains files used for security management. These include the security policy (java.policy) and security properties (java.security) files.

c:\jdk1.7.0\jre\lib\applet

Jar files containing support classes for applets can be placed in the lib/applet/ directory. This reduces startup time for large applets by allowing applet classes to be pre-loaded from the local file system by the applet class loader, providing the same protections as if they had been downloaded over the net.

c:\jdk1.7.0\jre\lib\fonts

Contains TrueType font files for use by the platform.

Labels:

Popular posts from this blog

Primitive Obsession with Example

Primitive Obsession is the name of a code smell that occurs when we use primitive data types to represent domain ideas. For example, we use a string to represent a message or an integer to represent an amount of money. For Example: Code with Primitive Obsession // primitiveObsession.java public class primitiveObsession { public static void main ( String args []) { Integer [] cityPopulations = { 13000000 , // London 21903623 , // New York 12570000 , // Tokyo 1932763 , // Stockholm 1605602 , // Barcelona 4119190 // Sydney }; for ( Integer cityPopulation : cityPopulations ) { System . out . println ( cityPopulation ); } } } public class City { private final String name ; private final int population ; private final Continent continent ; public String getName () { return name ; } public int getPopulation () { return population ; } public Continent ge...
Read more

Factory Pattern

This pattern is used when it must be decided at run time which one of several compatible classes is to be instantiated. For example, the abstract Collator class's getInstance() method returns a collation object that is appropriate for the default locale, as determined by java.util.Locale.getDefault() : Like other locale-sensitive classes, you can use the static factory method, getInstance, to obtain the appropriate Collator object for a given locale.  The following example shows how to compare two strings using the Collator for the default locale. Compare two strings in the default locale Collator myCollator = Collator.getInstance(); if( myCollator.compare("abc", "ABC") < 0 ) System.out.println("abc is less than ABC"); else System.out.println("abc is greater than or equal to ABC");
Read more

Create AEM Project using Maven Archetype 11

Let's start with our journey of Adobe Experience Manager project development. I am using AEM 6.3, Java 1.8 and Maven 3.2 . Follow below steps and try to replicate the same at your end. Let know of any issues if you face in the comment section. Go to your project path and validate the commands mvn -v and java -version are pointing to the accurate installation of Maven and JDK. Type below command to start: "mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeGroupId=com.adobe.granite.archetypes -DarchetypeArtifactId=aem-project-archetype -DarchetypeVersion=11 -DarchetypeCatalog=https://repo.adobe.com/nexus/content/groups/public/" Once this is done downloading the dependency and starts creating folder structure, it will ask you for the required information. You can refer below information that I have given, you need to use yours based on your requirement or client need.  Define value for property 'groupId': : first-project-aem De...
Read more