Conor,

Thanks very much for your prompt reply. I figured it out - it was just a silly mistake on my part. I didn't end my manifest file with a blank line, so it didn't recognize the final attribute, which in my case was the Class-Path. I added a newline after that, and it worked without issue.

Thanks again for your help!

Regards,

-Andrew

Conor MacNeill wrote:

Andrew,

It's a while since I worked on the ejb tasks, so forgive me if I'm a
little hazy.

Andrew Perez-Lopez wrote:
I got the manifest attribute to work, but not completely.  It seems to
ignore my Class-Path attribute.  When I use the jar task with the same
manifest attribute, it creates a jar with the proper attributes, but the
ejbjar task seems to ignore Class-Path (though it catches other ones).
Here's the ant I'm using for the ejbjar:

      <ejbjar
          srcdir="${build.dir}"
          destdir="${build.dir}"
          naming="directory"
          descriptordir="${deployment-descriptor.dir}/"
          dependency="full"
          manifest="${deployment-descriptor.dir}/manifest.mf"
          >
          <jboss />
          <classpath>
              <fileset dir="${lib.dir}" >
                  <include name="*.jar" />
              </fileset>
          </classpath>
          <include name="**/*ejb-jar.xml" />
      </ejbjar>

Here's the manifest file (the quotes are to help capture white-space,
they're not actually in the file)

'Manifest-Version: 1.0
Created-By: Me
Class-Path: heyya.jar'

And here's what is in the jar's when ejb-jar's done:

'Manifest-Version: 1.0
Created-By: Me


I'm not sure what is going on there. <ejbjar> uses the standard JDK
classes for writing jars - namely JarOutputStream and Manifest and it
should accept Class-Path entries. The manifest is read in from the file
using
   manifest = new Manifest(in);
and the Jar is created with
   jarStream
     = new JarOutputStream(new FileOutputStream(jarfile), manifest);

Any ideas on how to get the classpath to show up there?  Also, you
mentioned per-bean manifests.  As that's not documented either, do you
have any hints for how that works, or any references to give?


The per-bean system depends on the naming scheme you employ. Since you
have set naming="directory", you should be able to put a manifest.mf
file into the same directory as the deployment descriptor and ejbjar
should find it.

Conor

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--

Andrew Perez-Lopez
Developer
BBN Technologies
[EMAIL PROTECTED]
(703) 284-1256



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to