Hi Sharad
A JAR file manifest consists of a main section followed by a list of sections for individual JAR file entries, each separated by a newline. Both the main section and individual sections follow the section syntax specified above. They each have their own specific restrictions and rules.
The main section contains security and configuration information about the JAR file itself, as well as the application or extension that this JAR file is a part of. It also defines main attributes that apply to every individual manifest entry. No attribute in this section can have its name equal to "Name". This section is terminated by an empty line.
The individual sections define various attributes for packages or files contained in this JAR file. Not all files in the JAR file need to be listed in the manifest as entries, but all files which are to be signed must be listed. The manifest file itself must not be listed. Each section must start with an attribute with the name as "Name", and the value must be a relative path to the file, or an absolute URL referencing data outside the archive.
If there are multiple individual sections for the same file entry, the attributes in these sections are merged. If a certain attribute have different values in different sections, the last one is recognized.
Attributes which are not understood are ignored. Such attributes may include implementation specific information used by applications.
Manifest Specification:
manifest-file: main-section newline *individual-section
main-sect ion: version-info newline *main-attribute
version-info: Manifest-Version : version-number
version-number : digit+{.digit+}*
main-attribu te: (any legitimate main attribute) newline
individual-section: Name : value newline *perentry-attribute
perentry- attribute: (any legitimate perentry attribute) newline
newline : CR LF | LF | CR (not followed by LF)
digit: {0-9}

Answered by laks , an ibibo Master, at 3:46 PM on May 21, 2008

The manifest is a special file that can contain information about the files packaged in a JAR(Java Archive) file. By tailoring this "meta" information that the manifest contains, you enable the JAR file to be used for a variety of purposes.When a JAR file is created with version 1.2 of the Java Development Kit, the default manifest file is very simple. Here are its full contents:
The manifest can also contain information about the other files that are packaged in the archive. Exactly what file information is recorded in the manifest will depend on what use you intend for the JAR file. The default manifest file makes no assumptions about what information it should record about other files, so its single line contains data only about itself.
To create the manifest file:

1. Create a new plain text file called MANIFEST.MF or open an existing manifest file and save it in your extension’s META-INF directory.
2. Define the manifest file. This includes:
* Manifest-Version – The version of the manifest.
* Archiver-Version – The name and version of the archiver application.
* Created-By – The Java™ project build manager application.
* Built-By – The author of the plugin.
* Build-Jdk – The version of the JDK.
For example:

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: Donovan VanderLindell
Build-Jdk: 1.5.0

3. Define the name of the extension that contains this pipe. By convention, this should match the filename.

For example: Extension-Name: integrator.solution.pdm6.sampl e or Extension-Name: integrator.customsolution.impl .
4. Define the title and vendor of the extension.
For example:

Specification-Titl e: Workplace Forms Server Platform Solution
for PDM 6.0 Sample
Specification-Vendor: IBM

5. Define the vendor, file name, and version of the extension implementation. The Implementation-Title must be the same as the Extension Name.
For example:

Implementation-Ven dor: IBM
Implementation-Title: service.platform.solution.pdm6 .samp le
Implementation-Version: 2.7.0

6. Declare the bundle version.
For example:

Bundle-Version: 2.7.0

7. Declare the service component. This must be the full path to the pipe’s activator file. If the bundle this manifest describes contains multiple pipes, use a comma separated list to define each activator.xml file.
For example:

Service-Component: OSGI-INF/LoadFormPipeActivator .xml

8. Declare the bundle’s manifest version and bundle vendor.
For example:

Bundle-ManifestVer sion: 2
Bundle-Vendor: IBM

9. List the packages that the pipe requires. If your bundle contains multiple pipes, ensure that you list all the packages required by all your pipes.
You must always add the following packages.

Import-Package: com.ibm.form.platform.base.pip es,
com.ibm.form.platform.ser vice.form,
com.ibm.form.platf orm.service.frame work.exception,
com.ibm.form. platform.service.pipes ,
org.apache.commons.logging

Add additional, comma-separated packages as necessary.
Note: You do not have to add java.* to this import list because it is always implied.
10. Define the name of the pipeline bundle. This must be the same as the extension name and implementation title.
For example:

Bundle-Name: service.platform.solution.pdm6 .samp le

11. Define the bundle classpath.
Normally, this is:

Bundle-Classpath: .

However, if you want to embed another JAR inside your bundle JAR, you need to add the embedded JAR name to this entry.
For example:

Bundle-Classpath: .,mail.jar

12. Describe the pipeline bundle. This entry is typically the same as the specification title.
For example:

Bundle-Description : Workplace Forms 2.7 Integrator for WebSphere
Portal 6.

Answered by shaista , an ibibo Master, at 4:06 PM on May 16, 2008

hi singh Manifest is an XML based, database driven Content Management System (CMS) for satisfying corporate communications needs, including Internet and Intranet.Traditional web development packages focus on creating a Website one page at a time, often immersing the author in complex HTML code. With manifest, anyone who can create and save documents in Microsoft word can create or maintain content for an Internet or Intranet site. Once the system is set up, you simply save a document to the system and the pages are automatically published to a site with the correct 'look and feel'. Simple. In its most basic form it is a simple to use system for creating and maintaining Internet and Intranet sites. In it's complete form, Manifest is a management system for all your online publishing needs. It is flexible, scalable and completely user customisable in terms of document data structure, and published website structure & layout. Administration is via a simple drag & drop based interface. Data is saved as XML and binary information, and reprocessed using XSL transforms. This allows Manifest to simultaneously publish data in a wide variety of formats instantly including HTML, CHTML for Imode, text, WML for WAP, PDF and many more, without the need for any more work! Data is abstracted from the published versions allowing the same data to be easily reused in a number of different situations and contexts. The Server side software is 100% JAVA so can run on any JAVA enabled computer. Client Communication is 100% HTTP(S) so the system is entirely transparent to firewalls.
for more inf check source http://www.hardlight.com.au/page?pg =11&stypen=rss

Answered by raj u , an ibibo Master, at 1:57 PM on May 16, 2008

On the Java platform, a manifest file is a specific file contained within a JAR archive. It is used to define extension and package related data. It is a meta data file that contains name-value pairs organized in different sections. If a JAR file is intended to be used as an executable file, the manifest file specifies the main class of the application. The manifest file is named MANIFEST.MF.

When a JAR file is created, it automatically receives a default manifest file. There can be only one manifest file in an archive, and it necessarily has to be in the META-INF directory. When a JAR file is created with version 1.2 of the Java Development Kit, the default manifest file is very simple.

Answered by Hem@nt , an ibibo Master, at 10:19 AM on May 16, 2008

Hi Sharad
A JAR file manifest consists of a main section followed by a list of sections for individual JAR file entries, each separated by a newline. Both the main section and individual sections follow the section syntax specified above. They each have their own specific restrictions and rules.
The main section contains security and configuration information about the JAR file itself, as well as the application or extension that this JAR file is a part of. It also defines main attributes that apply to every individual manifest entry. No attribute in this section can have its name equal to "Name". This section is terminated by an empty line.
The individual sections define various attributes for packages or files contained in this JAR file. Not all files in the JAR file need to be listed in the manifest as entries, but all files which are to be signed must be listed. The manifest file itself must not be listed. Each section must start with an attribute with the name as "Name", and the value must be a relative path to the file, or an absolute URL referencing data outside the archive.
If there are multiple individual sections for the same file entry, the attributes in these sections are merged. If a certain attribute have different values in different sections, the last one is recognized.
Attributes which are not understood are ignored. Such attributes may include implementation specific information used by applications.
Manifest Specification:
manifest-file: main-section newline *individual-section
main-section: version-info newline *main-attribute
version-info: Manifest-Version : version-number
version-number : digit+{.digit+}*
main-attribute: (any legitimate main attribute) newline
individual-section: Name : value newline *perentry-attribute
perentry-attribute: (any legitimate perentry attribute) newline
newline : CR LF | LF | CR (not followed by LF)
digit: {0-9}

Answered by jaivir , an ibibo Master, at 7:55 AM on May 16, 2008

The manifest file describes the pipe and the extension it is part of, as well as providing implementation, bundle, classpath, and service component information.

Most importantly, it lists which services to start and the packages you must import that will be used by the classes within the bundle that are external to the JAR. You must list every required package and ensure that the names are entered correctly or your pipe will not work.

Note: A manifest file can describe multiple pipes. You only need a single manifest file for your entire JAR. You need one manifest file for each bundle you deploy.

To create the manifest file:

1. Create a new plain text file called MANIFEST.MF or open an existing manifest file and save it in your extension’s META-INF directory.
2. Define the manifest file. This includes:
* Manifest-Version – The version of the manifest.
* Archiver-Version – The name and version of the archiver application.
* Created-By – The Java™ project build manager application.
* Built-By – The author of the plugin.
* Build-Jdk – The version of the JDK.
For example:

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: Donovan VanderLindell
Build-Jdk: 1.5.0

3. Define the name of the extension that contains this pipe. By convention, this should match the filename.

For example: Extension-Name: integrator.solution.pdm6.sample or Extension-Name: integrator.customsolution.impl.
4. Define the title and vendor of the extension.
For example:

Specification-Title: Workplace Forms Server Platform Solution
for PDM 6.0 Sample
Specification-Vendor: IBM

5. Define the vendor, file name, and version of the extension implementation. The Implementation-Title must be the same as the Extension Name.
For example:

Implementation-Vendor: IBM
Implementation-Title: service.platform.solution.pdm6.samp le
Implementation-Version: 2.7.0

6. Declare the bundle version.
For example:

Bundle-Version: 2.7.0

7. Declare the service component. This must be the full path to the pipe’s activator file. If the bundle this manifest describes contains multiple pipes, use a comma separated list to define each activator.xml file.
For example:

Service-Component: OSGI-INF/LoadFormPipeActivator.xml

8. Declare the bundle’s manifest version and bundle vendor.
For example:

Bundle-ManifestVersion: 2
Bundle-Vendor: IBM

9. List the packages that the pipe requires. If your bundle contains multiple pipes, ensure that you list all the packages required by all your pipes.
You must always add the following packages.

Import-Package: com.ibm.form.platform.base.pipes,
com.ibm.form.platform.service.form,
com.ibm.form.platform.service.frame work.exception,
com.ibm.form.platform.service.pipes ,
org.apache.commons.logging

Add additional, comma-separated packages as necessary.
Note: You do not have to add java.* to this import list because it is always implied.
10. Define the name of the pipeline bundle. This must be the same as the extension name and implementation title.
For example:

Bundle-Name: service.platform.solution.pdm6.samp le

11. Define the bundle classpath.
Normally, this is:

Bundle-Classpath: .

However, if you want to embed another JAR inside your bundle JAR, you need to add the embedded JAR name to this entry.
For example:

Bundle-Classpath: .,mail.jar

12. Describe the pipeline bundle. This entry is typically the same as the specification title.
For example:

Bundle-Description: Workplace Forms 2.7 Integrator for WebSphere
Portal 6.0 Document Manager

13. Define the bundle’s symbolic name. This must be the sa

Answered by Ajay Pal , an ibibo Master, at 6:55 AM on May 16, 2008

The Manifest class is used to maintain Manifest entry names and their associated Attributes. There are main Manifest Attributes as well as per-entry Attributes. For more information on the Manifest format-
http://java.sun.com/j2se/1 .4.2/docs/guide/jar/jar.html

Answered by Nagendra , an ibibo Master, at 10:41 PM on May 15, 2008

Hi;
When you create a JAR file, it automatically receives a default manifest file. There can be only one manifest file in an archive, and it always has the pathname

META-INF/MANIFEST.MF

When a JAR file is created with version 1.2 of the JavaTM Development Kit, the default manifest file is very simple. Here are its full contents:

Manifest-Version: 1.0

This line shows that a manifest's entries take the form of "header: value" pairs. The name of a header is separated from its value by a colon. The default manifest shows that it conforms to version 1.0 of the manifest specification.

The manifest can also contain information about the other files that are packaged in the archive. Exactly what file information is recorded in the manifest will depend on what use you intend for the JAR file. The default manifest file makes no assumptions about what information it should record about other files, so its single line contains data only about itself.

The format of the default manifest file changed between versions 1.1 and 1.2 of the Java Development Kit. If you create a JAR file for the java.math package, for example, the JDKTM 1.1 default manifest file would look something like this:

Manifest-Version: 1.0

Name: java/math/BigDecimal.class
SHA1-Digest: TD1GZt8G11dXY2p4olSZPc5Rj64=
MD5-Digest: z6z8xPj2AW/Q9AkRSPF0cg==

Name: java/math/BigInteger.class
SHA1-Digest: oBmrvIkBnSxdNZzPh5iLyF0S+bE=
MD5-Digest: wFymhDKjNreNZ4AzDWWg1Q==

Li ke the JDK 1.2 manifest file, the JDK 1.1 manifest has an entry for Manifest-Version. The version number is the same, indicating that the manifest specification didn't change between versions 1.1 and 1.2 of the JDK software.

Unlike the JDK 1.2 manifest file, the JDK 1.1 manifest has entries for each file contained in the archive, including the files' pathnames and digest values. The pathnames are given as values of the Name header. Any headers that immediately follow a Name header without any intervening blank lines, pertain to the file specified by the Name header. In the manifest above, for example, the first Name header is followed by these lines:

SHA1-Digest: TD1GZt8G11dXY2p4olSZPc5Rj64=
MD5-Digest: z6z8xPj2AW/Q9AkRSPF0cg==

Be cause these lines follow the Name header without any intervening blank lines, you know that the digest values they specify are the digest values for the file java/math/BigDecimal.class.
D igest values are relevant only with respect to signing JAR files. In fact, that's why the digest information isn't in the JDK 1.2 default manifest -- it isn't always needed. To learn more about digests and signing, see the Signing and Authenticating JAR Files lesson.

Answered by kishore , an ibibo Master, at 8:36 PM on May 15, 2008

On the Java platform, a manifest file is a specific file contained within a JAR archive. It is used to define extension and package related data. It is a meta data file that contains name-value pairs organized in different sections. If a JAR file is intended to be used as an executable file, the manifest file specifies the main class of the application. The manifest file is named MANIFEST.MF.

Answered by Shivam , an ibibo Citizen, at 6:55 PM on May 15, 2008

A manifest file is a file contained within a JAR archive. It is used to define extension and package related data. It is a meta data file that contains name-value pairs organized in different sections. If a JAR file is intended to be used as an executable file, the manifest file must specify the main class of the application. The manifest file has to be named as MANIFEST.MF.

Answered by Nishu's , an ibibo Master, at 6:53 PM on May 15, 2008