You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Guven Demir <Gu...@telenity.com> on 2003/12/04 15:37:40 UTC

jsp:include :: no error when target page is missing

hi all,
 
i've noticed that jsp:include tag does not generate an error when the target page is not found. it simply does not include anything.
 
is there a way to change this behavior? i looked it up in the jasper configuration docs to find a way to affect how it generates the offending code to no avail. am i missing something?
 
by the way, do you know of or a pointer to any similar error prone behaviors of tomcat?
 
thanks in advance,
guven demir.

 


Guven Demir
Software Engineer<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Telenity A.S.

Tel.           +90.212.468.2057
Fax.          +90.212.465.0910 
guven.demir@telenity.com 


 <http://www.telenity.com/> www.telenity.com


IMPORTANT: The information contained in this e-mail and any attachment(s) may be privileged and confidential information intended only for the use of the entity named above. If the reader is not the intended recipient or the agent responsible to deliver it to the intended recipient, the reader is hereby notified that any disclosure, dissemination, distribution, copying or electronic or other storage of this communication is strictly prohibited. If you have received this communication in error, please immediately call us to collect.

 

 

Re: jsp:include :: no error when target page is missing

Posted by Bill Barker <wb...@wilshire.com>.
Since the spec forbids a jsp:include from changing the status or the headers, I don't really see an option around this.
  "Guven Demir" <Gu...@telenity.com> wrote in message news:566C72F44B0EFE46A5A133D248F8ED1601285EA5@mail.telenity.com.tr...
  hi all,

  i've noticed that jsp:include tag does not generate an error when the target page is not found. it simply does not include anything.

  is there a way to change this behavior? i looked it up in the jasper configuration docs to find a way to affect how it generates the offending code to no avail. am i missing something?

  by the way, do you know of or a pointer to any similar error prone behaviors of tomcat?

  thanks in advance,
  guven demir.


        Guven Demir
        Software Engineer

        Telenity A.S.
       Tel.           +90.212.468.2057
        Fax.          +90.212.465.0910 
        guven.demir@telenity.com 
       
        www.telenity.com
       
        IMPORTANT: The information contained in this e-mail and any attachment(s) may be privileged and confidential information intended only for the use of the entity named above. If the reader is not the intended recipient or the agent responsible to deliver it to the intended recipient, the reader is hereby notified that any disclosure, dissemination, distribution, copying or electronic or other storage of this communication is strictly prohibited. If you have received this communication in error, please immediately call us to collect.