Hi, I have come to hate the Websphere Test Environment. It seems to cache and never let go, take forever to restart, can't find drivers that are included in its classpath, never give any error messages, etc. Have others experienced these problems? If so what are the common work arounds? Thanks, Skip
If you love me, you will visit docs.opensimplatform.org
(FYI, Getting it tattooed on is a bit much.)
Originally posted by Skip Cole: Hi, I have come to hate the Websphere Test Environment. It seems to cache and never let go, take forever to restart, can't find drivers that are included in its classpath, never give any error messages, etc. Have others experienced these problems? If so what are the common work arounds? Thanks, Skip
I really like the WTE. Have you ever used an IDE that did not have a test environment (both a servlet engine and an EJB container) built in? I am currently being forced to use another IDE on a project that I am currently on. That IDE does not have either a servlet engine or an EJB container. If you want to talk about wasting precious development time try having to "deploy" between every little change, try to "debug" interactivly, the list goes on. Things that I have done in the past to "speed" up WTE starting include: 1) When working on projects that may have several different webapps, edit the default.servlet_engine file and only start the webapps that I want to work on. 2) I make sure that I do not "autostart" any servlets that do not require autostarting. As far as WTE not being able to find "drivers" or other "classes" I have never had a problem. The classpath is a tricky thing no matter what tool or Appserver you are using. I have always found that when WTE couldn't find a class it was always because I didn't add it to the classpath correctly. Well they say "you never really know what you had until its gone" I currently do not have the WTE and I for one miss it! [ January 25, 2002: Message edited by: Jeff Kinsey ]
Joined: Jan 05, 2001
Hi, It is possible, 4.5 months later, that it is better. I'll have to check it. Skip
I have always found WTE to be pretty solid, apart from when running on a machine with not enough RAM. Remember that when developing you are often running different types of software on one desktop PC, when in a production environment these apps would be distributed amongst multiple, more powerful servers. We expect a lot from our humble development machines. You may have VAJ, WTE (Servlet Engine, Persistent Name Server, and EJB Servers) and a database all running at the same time. I have found WTE to be a bit unpredictable on machines with 384KB or less RAM. Above that it seems OK, but then that is for the work I do. Your situation may be different.
I have used JBuilder 3 and VAJ 3.5.x as far as commercial IDEs. I have grown to like it more that JBuilder. The version control and method copy features are nice. 1. When i need to restart the Servlet engine i kill it from the debugger(5 seconds to stop) then I restart it. 2. The Error messages are consistent with WAS 3.5 (i.e. Ambiguous at Best). But it forced me to create a reliable exception/logger package so I have no complaints now. 3. Some times our sessions in WTE become invalid for no apparent reason. It is quite frustrating.
Here's a small annoyance that I have with the Visual Age 3.5.3 WTE: I have a few JSP pages that should not be cached by the browser, so I added the code:
The funny thing is this doesn't seem to make any difference when the pages are served from the WTE, but do behave properly when they are served from WebSphere 3.5 Fixpack 4 via IBM HTTP Server. Perhaps I'm missing something. Ultimately, the WTE has saved me heaps of grief. Hopefully I can become more familiar with WSAD soon. Regards, Ted Schrader, SCJP