ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie Bernard <>
Subject RE: Getting Local interfaces into an EJB using <ejbjar>
Date Tue, 26 Feb 2002 23:22:46 GMT
Not trying to pester, but does anyone have any insight or thoughts on this?
I'm sure *someone* has experienced this same problem before?

-----Original Message-----
From: Eddie Bernard []
Sent: Monday, February 25, 2002 4:39 PM
To: ''
Subject: Getting Local interfaces into an EJB using <ejbjar>

Has anyone else encountered this problem?

I have several EJBs that use local interfaces as prescribed by the J2EE (a
link to the tutorial explanation:

In my build file, I use the following:

    <ejbjar srcdir="${}"
      <weblogic destdir="${opel.release}"
      <dtd publicId="-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
      <include name="**/ejb-jar.xml"/>
      <exclude name="**/*weblogic*.xml"/>

With this, it generates the EJBs but does not include the Local interfaces
in the corresponding jar.  The only way that I can get this to work is using
the nested <support> element to include these classes, but since this target
iterates to create all EJBs it "bloats" every EJB jar with unnecessary Local
interface classes.

I'm currently using Ant 1.4.1 and I've tried using Ant 1.5 builds to do the
same, but 1.5 actually attempts to include extraneous support classes in the
EJB jar.  This, again, is bloating since I create a support classes jar file
which contains all pertinent support classes any EJB may need to reference.

The local interfaces are declared correctly in the deployment descriptors
(both generic and Weblogic-specific).  So, my assumption is that the task
should be "smart" enough to include the local interface classes pertinent to
the EJB jar it's creating during this step.

Does anybody have any ideas on this?


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message