JAR

In computing software, a JAR file (or Java ARchive) aggregates many files into one.[1] Software
developers generally use .jar files to distribute Java applications or libraries, in the form of classes and
associated metadata and resources (text, images, etc.) JAR files build on the ZIP file format. Computer
users can create or extract JAR files using the jar command that comes with a JDK. They can also use
zip tools to do so, however caution should be exercised as to the order of entries in the zip file headers
as the manifest likely needs to be first.

Jad

Java Application Descriptor (JAD) files describe the MIDlets (Java ME applications) that are
distributed as JAR files. JAD files are commonly used to package Java applications or games
that can be downloaded to mobile phones. Java applications enable Mobile phones to interact
programmatically with online web services, such as the ability to send SMS messages via GSM
mobile internet or interact in multiplayer games. Some BlackBerry devices use JAD files for
themes.

Recent midlets contain a manifest file in the JAR archive. This file contains much of the
information stored in the JAD file, rendering it unnecessary in most cases.

Sun Java Wireless Toolkit

Sun Java Wireless Toolkit (formerly J2ME Wireless Toolkit)

The Sun Java Wireless Toolkit (formerly known as Java 2 Platform, Micro Edition (J2ME)
Wireless Toolkit) is a state-of-the-art toolbox for developing wireless applications that are based
on J2ME's Connected Limited Device Configuration (CLDC) and Mobile Information Device
Profile (MIDP), and designed to run on cell phones, mainstream personal digital assistants, and
other small mobile devices. The toolkit includes the emulation environments, performance
optimization and tuning features, documentation, and examples that developers need to bring
efficient and successful wireless applications to market quickly

The J2ME Wireless Toolkit is a comprehensive set of tools for building MIDP applications. The
toolkit can be used standalone, or incorporated into many popular integrated development
environments (IDEs).

The Sun J2ME Wireless Toolkit supports the development of Java applications that run on
devices such as cellular phones, two-way pagers, and palmtops.
The project was initiated by Sun Microsystems team in Sun Israel Development Center in the
year 2000. The developers of the first version were Daniel Blaukopf, in charge of the internals
and Amir Uval on the User Interface

WAV

WAVE or WAV, short for Waveform Audio File Format,[6][3][7][8] (also, but rarely, named, Audio for
Windows[9]) is a Microsoft and IBM audio file format standard for storing an audio bitstream on PCs. It is
an application of the RIFF bitstream format method for storing data in “chunks”, and thus is also close to
the 8SVX and the AIFF format used on Amiga and Macintosh computers, respectively. It is the main
format used on Windows systems for raw and typically uncompressed audio. The usual bitstream
encoding is the Linear Pulse Code Modulation (LPCM) format.

Midi

MIDI (Musical Instrument Digital Interface), pronounced /ˈmɪdi/, is an industry-standard

protocol defined in 1982[1] that enables electronic musical instruments such as keyboard
controllers, computers, and other electronic equipment to communicate, control, and synchronize
with each other. MIDI allows computers, synthesizers, MIDI controllers, sound cards, samplers
and drum machines to control one another, and to exchange system data. MIDI does not transmit
an audio signal or media — it transmits event messages such as the pitch and intensity of musical
notes to play, control signals for parameters such as volume, vibrato and panning, cues, and
clock signals to set the tempo. As an electronic protocol, it is notable for its widespread adoption
throughout the music industry.

Note names and MIDI note numbers.

All MIDI compatible controllers, musical instruments, and MIDI-compatible software follow the
same MIDI 1.0 specification, and thus interpret any given MIDI message the same way, and so
can communicate with and understand each other. MIDI composition and arrangement takes
advantage of MIDI 1.0 and General MIDI (GM) technology to allow musical data files to be
shared among many different files due to some incompatibility with various electronic
instruments by using a standard, portable set of commands and parameters. Because the music is
stored as instructions rather than recorded audio waveforms, the data size of the files is quite
small by comparison. Individual MIDI files can be traced through their own individual key code.
This key code was established in early 1994 to combat piracy within the sharing of .mid files.

AMR
The Adaptive Multi-Rate (AMR or AMR-NB) audio codec is a patented audio data
compression scheme optimized for speech coding. AMR was adopted as the standard speech
codec by 3GPP in October 1998 and is now widely used in GSM and UMTS. It uses link
adaptation to select from one of eight different bit rates based on link conditions.

AMR is also a file format for storing spoken audio using the AMR codec. Many modern mobile
telephone handsets will allow you to store short recordings in the AMR format, both open source
and commercial programs exist (see Software support) to convert between this and other formats
such as MP3, although it should be remembered that AMR is a speech format and is unlikely to
give ideal results for other audio. The common filename extension is .amr. There also exists
another storage format for AMR that is suitable for applications with more advanced demands on
the storage format, like random access or synchronization with video. This format is the 3GPP-
specified 3GP container format based on ISO base media file format.[1]

J2ME

Java Platform, Micro Edition, or Java ME, is a Java platform designed for mobile devices and
embedded systems. Target devices range from industrial controls to mobile phones (especially
feature phones) and set-top boxes. Java ME was formerly known as Java 2 Platform, Micro
Edition (J2ME).

Java ME was designed by Sun Microsystems, now a subsidiary of Oracle Corporation; the
platform replaced a similar technology, PersonalJava. Originally developed under the Java
Community Process as JSR 68, the different flavors of Java ME have evolved in separate JSRs.
Sun provides a reference implementation of the specification, but has tended not to provide free
binary implementations of its Java ME runtime environment for mobile devices, rather relying
on third parties to provide their own.

As of 22 December 2006, the Java ME source code is licensed under the GNU General Public
License, and is released under the project name phoneME.

As of 2008, all Java ME platforms are currently restricted to JRE 1.3 features and uses that
version of the class file format (internally known as version 47.0). Should Sun ever declare a
new round of Java ME configuration versions that support the later class file formats and
language features, such as those corresponding JRE 1.5 or 1.6 (notably, generics), it will entail
extra work on the part of all platform vendors to update their JREs.

Java ME devices implement a profile. The most common of these are the Mobile Information
Device Profile aimed at mobile devices, such as cell phones, and the Personal Profile aimed at
consumer products and embedded devices like set-top boxes and PDAs. Profiles are subsets of
configurations, of which there are currently two: the Connected Limited Device Configuration
(CLDC) and the Connected Device Configuration (CDC).[1]
There are more than 2 billion Java ME enabled mobile phones and PDAs[2].

Connected Limited Device Configuration

Main article: Connected Limited Device Configuration

The Connected Limited Device Configuration (CLDC) contains a strict subset of the Java-class
libraries, and is the minimum amount needed for a Java virtual machine to operate. CLDC is
basically used for classifying myriad devices into a fixed configuration.

A configuration provides the most basic set of libraries and virtual-machine features that must be
present in each implementation of a J2ME environment. When coupled with one or more
profiles, the Connected Limited Device Configuration gives developers a solid Java platform for
creating applications for consumer and embedded devices.

[edit] Mobile Information Device Profile

Designed for mobile phones, the Mobile Information Device Profile includes a GUI, and a data
storage API, and MIDP 2.0 includes a basic 2D gaming API. Applications written for this profile
are called MIDlets. Almost all new cell phones come with a MIDP implementation, and it is now
the de facto standard for downloadable cell phone games. However, many cellphones can run
only those MIDlets that have been approved by the carrier, especially in North America[citation
needed]
.

JSR 271: Mobile Information Device Profile 3 (Final release on 09 Dec, 2009) specified the 3rd
generation Mobile Information Device Profile (MIDP3), expanding upon the functionality in all
areas as well as improving interoperability across devices. A key design goal of MIDP3 is
backward compatibility with MIDP2 content.

[edit] Information Module Profile

The Information Module Profile (IMP) is a profile for embedded, "headless" devices such as
vending machines, industrial embedded applications, security systems, and similar devices with
either simple or no display and with some limited network connectivity.

Originally introduced by Siemens Mobile and Nokia as JSR-195, IMP 1.0 is a strict subset of
MIDP 1.0 except that it doesn't include user interface APIs — in other words, it doesn't include
support for the Java package javax.microedition.lcdui. JSR-228, also known as IMP-NG, is
IMP's next generation that is based on MIDP 2.0, leveraging MIDP 2.0's new security and
networking types and APIs, and other APIs such as PushRegistry and platformRequest(), but
again it doesn't include UI APIs, nor the game API.

What ever duh?

[edit] Connected Device Configuration

Main article: Connected Device Configuration

The Connected Device Configuration is a subset of Java SE, containing almost all the libraries
that are not GUI related. It is richer than CLDC.

[edit] Foundation Profile

The Foundation Profile is a Java ME Connected Device Configuration (CDC) profile. This
profile is intended to be used by devices requiring a complete implementation of the Java virtual
machine up to and including the entire Java Platform, Standard Edition API. Typical
implementations will use some subset of that API set depending on the additional profiles
supported. This document describes the facilities that the Foundation Profile provides to the
device and other profiles that use it. This specification was developed under the Java Community
Process.

[edit] Personal Basis Profile

The Personal Basis Profile extends the Foundation Profile to include lightweight GUI support in
the form of an AWT subset. This is the platform that BD-J is built upon.

[edit] Personal Profile

The Personal Profile is an extension of the Personal Basis Profile, and includes a more
comprehensive AWT subset and adds applet support.

[edit] Implementations
Sun provides a reference implementation of these configurations and profiles for MIDP and
CDC. Starting with the JavaME 3.0 SDK, a Netbeans-based IDE will support them in a single
IDE.

In contrast to the numerous binary implementations of the Java Platform Sun provides on server
and workstation machines, Sun does not provide any binaries for the platforms of Java ME
targets with the exception of an MIDP 1.0 JRE (JVM) for Palm OS.[3] Sun provides no J2ME
JRE for the Microsoft Windows Mobile (Pocket PC) based devices, despite an open-letter
campaign to Sun to release a rumored internal implementation of PersonalJava known by the
code name "Captain America".[4] Third Party VM's like JBlend and JBed are widely used by
Windows Mobile vendors like HTC and Samsung

Operating systems targeting Java ME have been implemented by DoCoMo in the form of DoJa,
and by SavaJe as SavaJe OS. The latter company was purchased by Sun in April 2007 and now
forms the basis of Sun's JavaFX Mobile. The company IS2T provides Java ME virtual machine
(MicroJvm), qualified as baremetal, where the virtual machine is the OS/RTOS: the device boots
in Java.[5]
MicroEmulator provides an open source (LGPL) implementation of MIDP emulator. This is a
Java Applet based emulator and can be embedded in web pages.

The open-source Mika VM aims to implement JavaME CDC/FP, but is not certified as such
(certified implementations are required to charge royalties, which is impractical for an open-
source project). Consequently devices which use this implementation are not allowed to claim
JavaME CDC compatibilty.

[edit] Getting Started

 Java ME SDK (3.0), available at project download page

 NetBeans Mobility Pack, available at project home page
 Eclipse Mobile Tools for Java, available at project home page

ABOUT COMPANY

About Us

We are offering project training for the students in their final semester. My well qualified team
members, accompany the students throughout the project and make it come out the way they wanted
it to be. Also, let me not leave out mentioning that, at the end of the project, students hold not just the
project report at hand, but also substantial knowledge in the domain they worked in. Our training arena
mainly comprises of latest and leading technologies as follows:

we are the first institution offering live web designing course . In addition to this, we also
conduct free workshop in flexible time for students, week-ends.

WEB TECHNOLOGY:
CLIENT SIDE LANGUAGES:

 Html
 Javascript
 Vbscript
 Ajax
 E4x
 Xml

SERVER SIDE LANGUAGES:

 Php
 Servlets
 Jsp
 Asp
 Asp.net with C#
 Asp.net with VB
 Perl
 Python
 Applets
 CGI
 ADO.net
 Web Services

DATABASES:

 Oracle
 Ms Access
 Ms Sql
 Mysql
 Db2
 Xml

TOOLS USE FOR WEB DESIGHNING:

 Visual Studio 2005

 Netbeans 5.5
 Php desighner 2009
 FrontPage
 Dreamweaver
 Microsoft Publisher 2007
 Web Page Maker
 Photoshop
 Flash

SERVERS USE FOR SERVER SIDE SCRIPTING LANGUAGES:

  Apache Tomcat
 Wamp Server
 Xampp Server
 IIS
 www.monsterwinservers.com (FOR LIVE WEB DESIGHNING)

SYSTEM APPLICATION PROJECTS:

 VB.net
 VB6.0
 Java
 VC#.net
 VC++.net
 Back end same as mentioned for web technology.

PROGRAMMING LANGUAGES:

 C
 C++
 Java
 C#
 J2EE
 J2SE
 J2ME

OUR CURRENT PROJECTS:

 A website named “Chennai Smart City” containing a complete information about Chennai for
Chennai corporation.
 Our website “Chennai Corporate Kings” for Cricket League “cck-2010” which is expected to be
held in the month of January 2010
 Application softwares such as Supermarket Billing Software, Data entry corrector software,
College Management System, Library Management System, Student Database , and students
final year projects.
 Web designs for Travel agency, hotels, Small Business, etc.
 Website for a boarding school in Erode named "Ideal, Adharsh".