Todd- So, if are you saying that the manifest file name must have the name of the EJB as specified in the deployment descriptor?
If so, then does the name of the manifest and directory structure look like: META-INF/ ejb-jar.xml MyBeanName-manifest.mf or does the manifest simply need to be "Manifest.mf". Better yet, is this case-sensitive? Cheers! Eddie -----Original Message----- From: Todd Chambery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 5:41 PM To: Ant Users List Subject: Re: Adding/extending a manifest using <ejbjar> Howdy, The GenericDeploymentTool in CVS (http://cvs.apache.org/viewcvs/jakarta-ant/src/main/org/apache/tools/ant/tas kdefs/optional/ejb/GenericDeploymentTool.java) has a workaround in which <ejbjar> will pick up your manifest if it is named with descriptor_root_dir/base_name-manifest.mf . I don't quite understand why GDT doesn't just look to see if a "manifest.mf" exists in the current descriptor directory, and if it does, add it to the jar. If one isn't there, put in the empty Ant default. I'm going to make an attempt at submitting a patch (I think it's a very simple fix). hope that helps, Todd ----- Original Message ----- From: "Eddie Bernard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 09, 2002 7:54 PM Subject: Adding/extending a manifest using <ejbjar> > OK, I've haven't completely given up on using <ejbjar> for my WebLogic 6.1 > project. > > The reason I want to use it is that I have approximately 75 EJBs that I want > to build and the target I've created that uses <ejbjar> neatly creates each > EJB with only one target. Using some of the other suggested methods > (which, again, I appreciate the responses) would require me to have a target > for virutally every bean and even worst add more targets if more beans are > added to the project. > > Now with all tht said, I'm in the process of creating an Enterprise Archive, > but I'm having a deployment problem -- again unrelated to Ant itself. > However, after reading some BEA white papers and the J2EE specifications for > Application Deployment, it allows the addition of the name:value pair: > > Class-Path: list-of-jars-separated-by-spaces > > Example: > > Class-Path: lib/my_support_classes.jar > > Now the Ant-related problem... It seems that <ejbjar> extends the <jar> task > meaning that it inherits the "manifest" attribute. If I use <jar> with my > manifest addition it works just fine. However, with <ejbjar> it generates a > "near empty" file (actually, it has a set of cr/lf). > > Has anybody else come across this problem or have any ideas what I can do? > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
