Ultimately, yes, the deployment descriptors get named as ejb-jar.xml in the META-INF directory for the deployed ejb. According to the ant documentation there's a descriptor naming convention which names the deployment descriptors BeanName-ejb-jar.xml and BeanName-weblogic-ejb-jar.xml. This convention is also in an article at onjava.com as well as other places: http://www.onjava.com/pub/a/onjava/2001/06/25/antejb.html
Our project moved to this convention when we moved from having an individual build.xml for each ejb. Those build files manually jarred up the classes and called weblogic's ejbc using the ant java task. Doing a complete rebuild was very time consuming. We moved to using the ejbjar task, but our initial implementation of the task used the BeanName naming convention and worked nicely. I don't think it's that uncommon of a naming convention, as I've seen other groups in our company using this convention. Since we only have about 17 ejbs, it won't be such a challenge to switch to the ejb-jar.xml naming convention. That said, it would be really nice if the deploymentdescriptor task could be more flexible in both the filenames that it uses for creating the descriptors. The ejbjar task provides quite a few different naming conventions. It would also be nice if the deploymentdescriptor task would be able to automatically generate one deployment descriptor be ejb and not one descriptor per all ejb's it finds in the fileset given to the ejbdoclet task. I don't think it's that uncommon for projects to deploy one jar per bean to their container. -----Original Message----- From: Andrew Stevens [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2003 8:00 PM To: [EMAIL PROTECTED] Subject: Re: [Xdoclet-user] deploymentdescriptors - file naming convention On Tue, 2003-09-23 at 16:28, Mark Lybarger wrote: > I've been looking for a way to get around this using standard ant tasks, but > I'm not sure if it's workable. > > i'd like to give the output of the deploymentdescriptor task to be just the > ejb-name, not > <ejb-name>Bean-ejb-jar.xml, etc. This is because the ejb jar files that we > deploy are named beanName.jar and not beanNameBean.jar. The ejb-jar task > lets me specify to use the ejb-name from the deployment descriptors when > creating the ejb jar file, but when i use that it's looking for deployment > descriptors name ejb-jar.xml (without the bean name as part of the file). > here's my current deployment descriptor task. > > <deploymentdescriptor > destinationFile="{0}-ejb-jar.xml" destDir="${basedir.webapp.web-inf.src}"/> The deployment descriptor should *always* be named ejb-jar.xml, and be found in the /META-INF directory in your ejb jar. That's what the EJB spec says, and they're unlikely to deploy correctly otherwise. That's why the default destinationFile value is "ejb-jar.xml" for that subtask. Why would you want to do any different? Or have I misunderstood your question? Andrew. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
