A little guidance to everyone

[Guest.Visitor]

Joe, I missed diary #1, but this seems very useful. You mention that servlets get corrupted, are they associated with JSP pages? That is where I have seen problems, but all of our servlets are in Jar files, never thought it could be related to how they were deployed. David Morris

[J.Pluta]

This kind of thing will eventually be on my website, but until then, here's a little taste of the "zappie diaries" : ------- Diary #2: WebSphere Classpaths After a lot of work, I have determined the following: 1. JAR files can be either on the application classpath or in the properties file. The correct properties file is the one in /QIBM/UserData/properties (note that it is in UserData, NOT ProdData!) 2. JAR files in the application classpath will reflect changes automatically, without any need to restart the server. 3. JAR files in the properties file require at least a bounce of the server, and may require a bounce of QEJBSBS, depending on how they are accessed. 4. Servlets in jar files in the application classpath get CORRUPTED when a change is made. This is the worst thing about the whole mess. IBM ought to be able to fix this - I think this is a bug. Anyway, the correct way to do things SEEMS to be the following: A. Put your JAR files that change on your application classpath. B. Put your servlets directly into a directory on your application classpath (NOT in a jar file) If you want to use your properties file, fine, but that can cause extra work for no good purpose. Joe