You need to add <include> and <exclude> elements to select only the generic
descriptors. The vendor descriptors should be picked up automatically by the
vendor element. The doco has an example for the weblogic element.

Conor


> -----Original Message-----
> From: David M. Johnson [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 29 August 2001 1:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Status of optional Borland EJB task in 1.4b2 ?
>
>
> Ok, I got the latest Borland EJB stuff from CVS and I'm getting much
> farther, but I'm still not quite ready to rip out my own Borland EJB
> generator task quite yet.
>
> The jars built by the <ejbjar> task contain two ejb-jar.xml files and
> both of them contain the contents of my ejb-inprise.xml file.  Obviously
> the verifier does not like this very much.  I think the problem is in
> GenericDeploymentTool.java in processDescriptor().
>
> Seems like the ejb-inprise.xml file is getting added to the ejbFiles
> hashtable twice - once under the name 'ejb-jar.xml' and once with the
> key 'ejb-inprise.xml'
>
> Any ideas for a fix or a work around?  Thanks for your help so far.
>
>
> Here is my ejbjar code:
>
>     <ejbjar basejarname = "ejbutils"
>                  srcdir = "${ro_build}/temp"
>                 destdir = "${build.stage_beans}"
>           descriptordir = "${ejbutils.home}/src/etc/DeployEJB/META-INF">
>
>     <dtd publicId="-//Inprise Corporation//DTD Enterprise
> JavaBeans 1.1//EN"
>             location="file:./deploy/ejb-inprise.dtd"/>
>
>     <dtd publicId="-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
> 1.1//EN"
>             location="file:./deploy/ejb-jar.dtd"/>
>
>         <borland destdir = "${build.stage_beans}"
>                   suffix = "_basd.jar"
>                   verify = "true">
>             <classpath>
>                 <path location="${ro_build}/temp"/>
>                 <path refid = "borland.path"/>
>             </classpath>
>         </borland>
>
>         <support dir="${ro_build}/temp" />
>
>     </ejbjar>
>
>
> - Dave
>
>
>
>
>
>

Reply via email to