« OFM 11g: Starting WebLogic Server with opmnctl | Main | Book Review: Getting Started with Oracle SOA Suite 11g R1 »

Revisited: Including a Class-Path In Your MANIFEST.MF

In January 2008 I wrote about putting additional information into your Manifest.mf (see original entry). Recently a colleague told me that this does not work as expected in JDeveloper 11.1.1.1.0.

A short investigation showed that JDeveloper 11.1.1.1.0 does two things while going through the deployment process.

  1. It checks the correctness of the tag and its usage.
  2. It expects a value in the same line as the tag.

The first is nice and necessary to avoid any surprises. The second is a bit surprising if you follow my advise in having a separate line per Class-Path element. To get it work as in the original post, you need to be sure that every multi-line tag entry must have the form <tag>: <first_value> in the first line. For example:

Class-Path: ./lib
  commons-lang.jar
  etc.

About This Entry

This page contains a single entry from the blog posted on October 21, 2009 5:19 PM.

The previous post in this blog was OFM 11g: Starting WebLogic Server with opmnctl.

The next post in this blog is Book Review: Getting Started with Oracle SOA Suite 11g R1.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Powered by
Movable Type and Oracle