> The former option frees the individual desktops from the burden of running
the JVM and the J2EE application...
Do you mean the LATTER option (common server)?
I'd go with the central server approach, especially if you team is big (over
5) or specialized (java and web developers).
> the whole application has to be shut-down and redeployed
Just because you have one physical server does not mean you are limited to
running one app server instance on it for everyone. And furthermore, good
investment in a source control software which allows branching will pay
divident. For example in our dev environment each java developer has
his/her code branching running on his/her own app server running on a
centralized box, and source synchronization is managed by Perforce.
Furthermore we have a "stable" app server shared by all JSP/HTML developers,
also running on the same box.
This is a best-of-both-worlds solution: centralized server environment,
disparate app server sub-environment.
Gene Chuang
Kiko.com
-----Original Message-----
From: Alvaro Mota [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 5:23 AM
To: [EMAIL PROTECTED]
Subject: Question About Development j2ee - EJB spec 2.0
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".
==========================================================================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".
