Netscape has released their newest webserver, IPlanet 4.1 which boasts
support for JSP 1.1. It is definitely a big relief! Finally, a poor
developer like me can write code in JSP 1.1.
Unfortunately, it never gets simple tho. Following is an excerpt from the
release notes.
....
388728. JSP file changes are not reflected by the server.
Any changes you make to JSP files are not updated by the iPlanet Web
Server.
Workaround: delete the corresponding class file from the ClassCache
directory for that instance whenever a JSP file
changes.
....
(Thanks, It really helps! Have anybody looked into the classcache folder?
There are so many files with obscure folder names! )
My question is :-
1. How can you miss something like this??
2. In an earlier version of IPlanet (4.0, I believe ), I struggled with
session timeout and later found out that it was a bug. The problem was that
the session was getting timed out irrespective of the last accessed time.
Yes, the software is inherently complex. You can't solve all the problems..
blah.. blah. But there are some basic functionalities you expect out of any
software system. In this case, anybody implementing the session timeout, how
can you miss last accessed time? Similar is the case with JSP modified
files!
May be this is just me. Sorry, if this is not the appropriate newsgroup.
Sree
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
