Having been through a couple of these - here's the
process I've found works best:
- Everyone runs a copy of THE FULL APP on their
machine.
- Everyone checks out from source control daily and
builds. Use Ant for builds. Make sure people are
working with the latest code - especially in your case
where there are shared classes.
- Don't check in code to source control unless you've
done a full build on your local machine first (minimum
requirement).
- Perform Integration/QA builds on a central machine
that is as similar to the target production
environment as you can get. Increase the frequency of
these builds as the project progresses.
Also - be very careful about using the reference
implementation for development and then deploying on a
different platform. It's very likely that you'll find
that the code needs to be changed to get it to run on
the target app server - and then once you've changed
the code to run on the target server it will no longer
run on the reference implementation. I've heard of
some people getting this to work, but it will slow
development especially at the beginning of the project
while you figure out the problems.
Pick your app server as soon as you can and get it
installed on the developer machines - even if you have
to buy licenses for each developer. Either that or
plan on maintaining two version of the app - one that
runs on the target platform and one that is tailored
to the reference implementation platform.
I spoke to some people at iPlanet when we were kicking
off one project based on the iPlanet App Server. They
told me that they internally had developers doing
development on local desktops and did integration
centrally.
I've been on projects where we tried to do development
centrally for various reasons, but have always found
that things go much faster if each developer has their
own environment.
Good luck -
Kevin Bedell
http://www.kbedell.com
--- Alvaro Mota <[EMAIL PROTECTED]> wrote:
> This is question regarding the development process
> using EJB spec 2.0
> We are currently developing an application using
> EJB2.0, with a web
> interface (JSP). We are a 7 people team, each one in
> charge of a module of
> the systems (all modules are interrelated, i.e. use
> each other�s beans). We
> are using Sun�s reference implementation of the J2EE
> server in the
> development stage, before we select a commercial
> AppServer for the
> production environment.
>
> Our question is whether, during the implementation
> stage (when we are
> creating, testing and debuging code), we should
> install and run the whole
> application in everyone�s owns computers, or we
> should all work in a common
> server.
>
> The former option frees the individual desktops from
> the burden of running
> the JVM and the J2EE application, and for this
> reason would be our preffered
> option. However we do not know how we can coordinate
> everyones development
> effort in a single environment, since apparently
> everytime someone has to
> test code, the whole application has to be shut-down
> and redeployed.
>
> What is Sun�s advice on the best practice regarding
> this issue ?
> Thanks.
>
> �lvaro
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED]
> and include in the body
> of the message "signoff EJB-INTEREST". For general
> help, send email to
> [EMAIL PROTECTED] and include in the body of the
> message "help".
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
