Talking about both JSP and EJB: Do you separate JSP and EJB development or do you put
them in one project?
If you separate JSP and EJB, it seems difficult to test the beans with multiple app
server instances and one JSP engine because it is tedious to cofigure the JSP engine
to point to a different app server (say you are using a jBoss/Resin combo). Should
each EJB developer have his/her JSP engine as well? Should EJB developers write their
own test pages?
--Forrest
On Sat, 21 Jul 2001 01:07:18 -0700, Gene Chuang <[EMAIL PROTECTED]> wrote:
>Yup, your right, it definitely depends on the know-how of the dev team.
>Centralized box always means Unix/Solaris/Linux, which means the majority of
>the development team has to be familiar with this environment. Our team of
>10 java developers all are comfortable with Unix and can develope through a
>telnet terminal w/ emacs or vi, while our 5 jsp developers cope with Samba
>and UltraEditor. If you have a less flexible team (i.e. 100% Windows
>bound), then client-side development is the only way to go!
>
>Gene
>
===========================================================================
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".
