Posts Tagged ‘classpath’

Things to know about Spring Download, Installation & Configuration

November 23, 2009 Leave a comment



Things to know about download/installation/configuration of Spring Framework:


The Spring Framework and container is packaged in several JAR files. Spring is a library(.jar files) of classes that will be packaged with and used by your Spring-enabled applications. Installing Spring involves adding one or more JAR files to your application’s classpath. It does not have an executable runtime. Therefore, Spring is more similar to a library like Jakarta Commons than an application server like JBoss.

How you make Spring available to your application’s classpath will vary depending on how you build and run your application. You may choose to add the Spring JAR files to your system’s classpath or to a project classpath in your favorite IDE (as we will see in the post on configuring Spring Framework with Eclipse). If you’re building your application using Ant or Maven, be certain to include Spring in your build’s dependencies so that it will be included in the project’s target deployment.


Downloading Spring:

There’s plenty of additional materials in Spring’s full distribution, including Spring’s API documentation, examples, and the full source code for the Spring Framework. Therefore, the first thing you’ll want to do is to download the full Spring distribution. Refer to Spring Framework Installation & Configuration post. When downloading Spring, you will have 2 main choices: you can either download a Spring distribution that comes with its own dependencies or you can download a distribution that contains only the Spring JAR files. Even though the former is a much larger download, its better to download the one that comes with dependencies so that you won’t have to hunt down other JAR files that your application needs.


Exploring the Spring distribution:

Once you’ve downloaded the distribution, unzip it to a directory on your local machine. The Spring distribution is organized within the directory structure described in the table below. Several of these directories contain the Spring source code. The aspectj/,mock/, src/, and tiger/ directories contain the source code that makes up the Spring Framework itself. Meanwhile, the test/ directory contains the unit tests used to test Spring Framework. Although it’s not essential to using Spring, you may want to venture around in these directories to see how Spring does its stuff.



The Spring developers are extremely talented coders and there will be probably a little something to learn by reviewing their code. The docs/ directory contains two important pieces of documentation. The reference document is an overview of the entire Spring Framework. Also, the JavaDocs for the entire Spring Framework can be found under docs/—you’ll probably want to add this as a bookmark in your web browser, because you’ll refer to it often. The samples/ directory contains a handful of sample Spring applications. Of particular note are the petclinic and jpetstore examples. Both of these applications highlight many important elements of the Spring framework.


Building your classpath: Read more…

Java Terminologies

September 6, 2009 Leave a comment


Few terminologies to be familiar with, before getting started with Java:


Java Platform:

The Java platform from Sun allows developing and running programs written in the Java programming language. The platform is not specific to any one processor or operating system, but rather an execution engine called virtual machine and a compiler with a set of standard libraries that are implemented for various hardware and operating systems so that Java programs can run identically on all of them.

The Java Platform consists of several programs, each of which provides a distinct portion of its overall capabilities. For example, the Java compiler converts Java source code into Java byte-code, an intermediate language to be executed by the virtual machine (JVM) and it is provided as part of the Java Development Kit (JDK). The Java Runtime Environment (JRE), complementing the JVM with a just-in-time (JIT) compiler, converts intermediate byte-code into native machine code on the fly. Also supplied are extensive libraries, pre-compiled in which are several other components, some available only in certain versions.

The essential components in the platform are the Java language compiler, the libraries, java language itself (Java API) and the runtime environment in which Java intermediate byte-code “executes” according to the rules laid out in the virtual machine specification. 

  Java Platform


The heart of the Java Platform is the concept of a “virtual machine” that executes Java byte-code. This byte-code is the same no matter what hardware or operating system the program is running under. The use of byte-code as an intermediate language permits Java programs to run on any platform that has a virtual machine available. Although Java programs are platform independent, the code of the Java Virtual Machine (JVM) that execute these programs is not so every supported operating platform has its own JVM.

The JVM is a crucial component of the Java Platform. It is a platform-independent execution environment that converts Java byte-code into machine language and executes it. Most programming languages compile source code directly into machine code that is designed to run on a specific microprocessor architecture or operating system, such as Windows or UNIX.

The JVM is an instance of the JRE (Java Runtime Environment) and comes into action when a Java program is executed. JVM can be obtained with JRE / JDK distribution.

Few functionalities of JVM are:-

  • Loading of class files (compiled java source code).
  • Verification of class files i.e., Class files should contain valid byte-code.
  • Interpretation of byte code and then run the program. 


JIT: Read more…

Java Installation & Configuration

August 18, 2009 4 comments



Java is freely downloadable from Sun’s website ( . What’s to decide is which version to chose? At the time of this post, recommended Java versions are 1.4 , 1.5 and 1.6. While Java 1.4 has been in the field for quiet few years and personified as a de-facto across wide range of applications and industry choice, Java 1.5 has made its advent to an extent that many Java applications across the globe are now migrating to 1.5. Reason being simple, Java is backward compatible and richer features of Java 1.5. While Java 1.4 has persisted to demonstrate reliability, Java 1.5 has proved to be more plenteous. Relatively recent arrival of Java 1.6 has its share of the buzz with more features in the kit. Now, we have a sneak peak into Java 1.7 available as well. With every new release, new features in Java will be explored. As this post’s focus is on the installation/configuration facet, we shall keep the discussion of java versions, features, pros & cons as an open topic.

Many times, there’s confusion about PATH / CLASSPATH/ JAVA_HOME variables. What they actually are and how they matter? Or if its really necessary to set them, if so how to set them? Below we try to answer all the questions that matter.

The following sections describe:-

  • Downloading Instructions – Describes where and what to to download.
  • Installing Instructions – Describes how to install Java into a location in the computer.
  • Configuration Instructions – Describes how to set up a computer to write java programs and also execute them.


In brief:

  • Download Java (JDK – if you want to write and run your own java programs / JRE – if you only want to run java programs) from Sun’s website. (Chose your java version)
  • Once downloaded, install Java to any location on your computer
  • Set environment variables (PATH / CLASSPATH / JAVA_HOME – all optional and set for convinience) in your computer.
  • Set PATH to (java installed location)/JDK_verstion/bin (optional)
  • Set CLASSPATH to (java installed location)/JDK_verstion/lib/tools.jar (optional)
  • Set JAVA_HOME to (java installed location)/JDK_verstion (optional)

If you are using any IDE for working on java, you dont even have to set the environment variables, as the IDE itself ships with a support for a Java version. You have to set the environment variables most likely in situations like:

  • You want to work with simple text editors like notepad
  • You want to work with certain java dependant softwares like Ant, Glassfish, Tomcat etc which need java environment variables to be set.

Refer below detailed description for more information.



Downloading Instructions: Read more…