Call for ideas: multiple EJB targets

[Jesse Tilly <JT...@hoteltools.com>]

Situation:
   Project with multiple EJBs.  Each bean has its own subdirectory for
storing its descriptor files.  The classes are packaged within the rest of
the source.  Each EJB class follows the convention of <bean name>Bean.java,
<bean name>PK.java.  This naming convention *should* allow me to have n
beans but the global build environment be unaware of any particular one by
name.  Due to uncertainty as to which 1.2 release is "most stable", I am
running Release 1.1.

My idea:
  Along with the descriptor files, each bean's directory will have its own
build.xml to provide for the ability to jar, ejbc, deliver and deploy
itself.  The project build file should be able to simply traverse a
directory tree of these descriptor directories.  Unfortunately, I cannot
find a facility within the <ant> tag that allows me to "run all build.xml
files below a certain directory".  Beyond that, I cannot think of any other
way to solve my problem.

Any ideas?

> J E S S E  E  T I L L Y
> Senior Programmer, Development
> ____________________________________________
> HotelTools, Inc.
> 100 Galleria Parkway, Suite 1020
> Atlanta, GA  30339
> ph: 770.956.4080 x5361
> fax: 770.956.4077
> cell: 678.524.5764
> http://www.hoteltools.com
> 
> 
 <<Jesse Tilly.vcf>> 

RE: Call for ideas: multiple EJB targets

[Conor MacNeill <co...@m64.com>]

Jesse,

We regularly build multiple EJBs with a single build file using the ejbjar
task. We do use the ejbjar naming convention to name the deployment
descriptors. You probably don't need to have a naming convention for the
bean and PK classes as these are specified in the deployment descriptor. A
naming convention for these is not a bad idea, just not required for
building.

Our setup is similar to your. Code in one tree, descriptors in another. That
is mandatory for us as we deploy the same bean code with different
deployment descriptors.

I would recommend against going to separate build files for each bean.

Let me know if you need more info.

Conor


> -----Original Message-----
> From: Jesse Tilly [mailto:JTilly@hoteltools.com]
> Sent: Friday, 13 October 2000 13:37
> To: 'ant-user@jarkarta.apache.org'
> Subject: Call for ideas: multiple EJB targets
>
>
> Situation:
>    Project with multiple EJBs.  Each bean has its own subdirectory for
> storing its descriptor files.  The classes are packaged within the rest of
> the source.  Each EJB class follows the convention of <bean
> name>Bean.java,
> <bean name>PK.java.  This naming convention *should* allow me to have n
> beans but the global build environment be unaware of any particular one by
> name.  Due to uncertainty as to which 1.2 release is "most stable", I am
> running Release 1.1.
>
> My idea:
>   Along with the descriptor files, each bean's directory will have its own
> build.xml to provide for the ability to jar, ejbc, deliver and deploy
> itself.  The project build file should be able to simply traverse a
> directory tree of these descriptor directories.  Unfortunately, I cannot
> find a facility within the <ant> tag that allows me to "run all build.xml
> files below a certain directory".  Beyond that, I cannot think of
> any other
> way to solve my problem.
>
> Any ideas?
>
> > J E S S E  E  T I L L Y
> > Senior Programmer, Development
> > ____________________________________________
> > HotelTools, Inc.
> > 100 Galleria Parkway, Suite 1020
> > Atlanta, GA  30339
> > ph: 770.956.4080 x5361
> > fax: 770.956.4077
> > cell: 678.524.5764
> > http://www.hoteltools.com
> >
> >
>  <<Jesse Tilly.vcf>>
>
>