I would recommend that in your process of selection that you make sure that
all features are available with all levels of virtual machine. Symantec
does'nt seem to provide that aspect.
-----Original Message-----
From: TKV Tyler VanGorder [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 05, 2000 1:05 PM
To: [EMAIL PROTECTED]
Subject: Re: IDE Reccomendations
>-----Original Message-----
>From: Clay Kasow [SMTP:[EMAIL PROTECTED]]
>Sent: 05 Jan 2000 9:18 AM
>To: [EMAIL PROTECTED]
>Subject: IDE Reccomendations
>
>Hello!
>
>I am planning on switching to using an IDE in the development of a
>Servlet/JSP based system I am working on. Currently, I am doing all of my
>coding using a plain old text editor. The complexity of the system has
>grown to the point where I am feeling like I could use a good tool to help
>me stay organized - I am hoping that the right IDE will help to reduce a
lot
>of the grunt work necessary when making changes to the core classes used by
>the system. I also am in need of a good debugger. I am looking for
>feedback about the pros and cons of various IDEs out there on the market.
I
>can see the usefulness of an IDE for building the GUI of a regular old
>applet, but a part of me feels that there is a tremendous amount of hype
>about how much an IDE can help with this sort of nitty gritty server side
>work. Will using an IDE actually be a tremendous improvement over coding
>with a text editor and compiling off the command line? Will a good IDE
>actually help me to use better object oriented design in my
>database-access-related utility classes, and the classes encapsulating the
>core business logic?
>
>To give you a sense of the design principles I am using in this system:
>
>1) As little Java as possible is put into JSPs. Only as much as is
>necessary to get values out of session parameters and format them for
>display. At some point, even this formatting will be handled by JavaBeans.
>2) No HTML is ever put into a Servlet. Servlets simply handle form
>requests and put objects into session variables for use by the formatting
>JSPs, which they then redirect to.
>3) No SQL, and a minimal amount of business logic, ever appears in
>Servlets. Rather, Servlets use utility objects which encapsulate the
>details of all database activity to do their work for them. At some point,
>these utility objects will simply be EJBs running on an application server.
>Right now, everything is being done from within the ServletEngines VM.
>
>I would hope that whatever IDE I was using would work well with this design
>philosophy.
>
>Thanks in advance for your ideas and stories about how various IDEs have
>helped, hindered, or had no effect on your development of Servlet/JSP based
>systems.
>
>-Clay
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
