OK, Asha. I just tested this and it worked fine for me. I create two JSPs with
the same content, but different names and different page directives. So one
page directive said:
<%@ page isThreadSafe="false" %> and the other said
<%@ page isThreadSafe="true" %>
I requested them and saw the output and made sure the class, java and lnt files
were in my application's WEB-INF/jsp directory. Then I stopped the JRun server,
closed my browser to clear the browser cache, deleted the source JSPs and the
java and lnt files for both pages. I restarted the server and opened a browser
and I hit both pages with no problem. So what gives?
I was testing this with the JRun SP1 that was released a couple weeks ago, but I
don't know of any bug fixes or problems in this area anyway. The only
difference between a JSP with that directive set to false and one without (or
set to true) is that the false settings makes the JSP servlet implement the
SingleThreadModel interface.
So what do you think? Do you have a simple test case? Should be easy to
reproduce. Try the SP1 RC if you're really desperate, but I think it must be
something else.
Scott Stirling
> -----Original Message-----
> From: Asha Sayd [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 13, 2000 2:33 PM
> To: [EMAIL PROTECTED]
> Subject: 404 ERROR:page not found when using "isThreadSafe=false" in JSP
> page
>
>
>
>
> hi,
>
> 404 page not found is generated when we try to deploy
> an application with jsp pages in which "isThreadSafe=false" is set.
> If we add .jsp files to the application, then the application works fine.
> But we just want the jsp class files to be included in the application.
>
> if we remove "isthreadsafe=false" and then recompile the class and
> deploy the application without .jsp files, the application works fine.
>
> Thanks in advance for any help.
>
> asha.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.