In a larger project. I divide the tasks up in ´bite-size´chunks to the
developers on the project, especially in the stage where the EJB´s have
to be developed. For simplicity I use NT as the development platform.
Each developer has his own instance of Weblogic with wich he can play at
will to test the bean. When I am confident the EJB´s are more or less
ready, I deploy them to the main instance of weblogic on the same server
for the web-tier development.
IMHO this is preferred to running an instance of weblogic on all the
workstations.
Sven
Shane Duan wrote:
> In our project, which is actually small size, it is not possible to have a
> centralized EJB testing environment because everyone is doing the deployment
> all the time. We installed the JRun testing server, which has the testing
> license key and allow max 3 connections. It was powerful enough for
> testing. We do have a central database server, though, because we don't
> really change the database that often.
>
> This has been working out fine for us and I would like to hear more input as
> well.
>
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Biske, Todd
> Sent: Thursday, March 08, 2001 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: Corporate EJB Development
>
>
> I'd like to hear how other medium to large IT organizations are architecting
> their development environments. IMO, the environment needs to be flexible,
> address (and minimize) licensing issues for the tools involvement, and
> support enterprise reuse of EJB's being developed.
>
> The main questions I'd like to get answers for is:
> Are the EJB developers in your organization developing EJB's on their own
> workstations?
> Within the project team, are EJB's deployed to a single development
> application server instance, having other developer who use those EJB's
> access via JNDI lookup and RMI based access, or does each developer deploy
> to their own local instance?
> Outside of the project team, how do other development teams (if at all)
> access and use those EJB's?
>
> Put another way, I'm wondering whether it makes sense to have a centralized
> home for EJB's in a development environment across the enterprise. If it
> does, what does that mean for the production environment, and what changes
> would be required as a project moves from development through
> integration/user acceptance testing and on to production?
>
>
> I appreciate any information anyone shares on how their organization may be
> doing things. I haven't seen any clear preferences on how an enterprise
> level EJB development environment should be set up.
>
> Thanks-
> -tb
>
>
> --------------------------------------------------------------
> Todd Biske [EMAIL PROTECTED]
> Java Mentoring Team (314) 955-6254
> A.G. Edwards & Sons, Inc. FAX: (314) 955-7324
>
>
>
> ****************************************************************************
> ***********
> WARNING: All e-mail sent to and from this address will be received or
> otherwise recorded by the A.G. Edwards corporate e-mail system and is
> subject to archival, monitoring or review by, and/or disclosure to,
> someone other than the recipient.
> ****************************************************************************
> ***********
>
> ===========================================================================
> 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".
>
>
===========================================================================
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".
