Both (multiple developer instances on centralized server vs. developer
instance on client box) have their merits; let me expound on the benefits
for the former:
1) Telecommute - this is KEY perk for all developers, and putting all
source codes and app servers on a VPN-able centralized server facilitates
this.
2) Easy to administer a homogenous, centralized environment. Installing a
new 3rd library jar, a new service pack for the app server or upgrading a
new jdk is trivial on a centralized server. I'm not sure why Kevin believes
administering and synchronizing multiple clients is easier than this,
perhaps he can explain.
3) Always-up - Individual instances on the centralized server are always
up. This is crucial for large, 2-tiered developement team consisting of app
and web developers. You do not want the scripters to deal with java code
and starting and stopping app servers at all, so they can work on their
always-up web server instance and connect to whichever app instance they
chose.
Gene
-----Original Message-----
From: Kevin Bedell
To: [EMAIL PROTECTED]
Sent: 7/20/01 12:59 PM
Subject: Re: Source Control for EJB Development/Deployment
Gene's suggestion is good but from my experience I've
found it easier for larger development teams to have
an instance of the app server installed locally for
development and testing. Then they can do whatever
they want before checking code in.
I believe it's worth it even if you have to buy
development licenses of the app server. You'll get the
money back in time savings.
I've worked in both environments and previously was a
proponent of centralized development - I just found
that the admin support required maintaining multiple
centralized instances of an app server is significant
and can become a bottle neck.
Plus if developers use windows on their desktops and
the central machine is solaris some of the junior team
members will be unproductive as they will need to work
in an environment they are unfamiliar with -
Whichever of the two solutions you pick the one thing
that is critical is to standardize the procedures for
installing a "developer instance" and make sure
everyone's environment is as identical as you can get.
Otherwise at integation time you'll spend 20% of your
time chasing configuration issues.
And whatever you do don't try to develop on one app
server (JBoss, tomcat, the j2ee reference
implmenetation) and the do integration on the actual
target platform.
Best of luck!
Kevin Bedell
http://www.kbedell.com
--- Gene Chuang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Our ejb development team works on a centralized
> server with perforce as
> source control, but each of us has our own app
> server instance running on
> the centralized box. I think this is the
> best-of-both-worlds solution.
>
> Gene
>
> -----Original Message-----
> From: Forrest Pan
> To: [EMAIL PROTECTED]
> Sent: 7/20/01 11:51 AM
> Subject: Source Control for EJB
> Development/Deployment
>
> Hi,
>
> We have multiple developers writing EJBs and we
> share one development
> EJB server. We are using a version control program
> (MKS), but the
> problem is when one developer finished his bean, he
> has to package it
> into the jar file and deploy it on the dev server.
> This can cause
> problems for other developers who are
> modifying/testing other beans.
> Unlike writing desktop applications where each
> programer can test his
> part on his own system, we aren't able to test the
> software before we
> merge our code. Can someone share his/her experience
> on solving this
> kind of problem?
>
> Your help is appreciated!
>
> --Forrest
>
>
========================================================================
> ===
> 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".
>
>
========================================================================
===
> 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".
===========================================================================
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".
