y want to consider changing your approach
>> to incorporate filters/servlets for some of your processing...
>>
>> On Wed, May 26, 2010 at 1:26 PM, laredotornado
>> wrote:
>>>
>>> I tried your suggestion, and sadly it didn't work.
>>>
>&
On Thu, May 27, 2010 at 12:54 PM, laredotornado wrote:
>
> You mean for me to put this at the top of my error page (500.jsp), correct?
> If so, I tried that, but still got the partially rendered page outlined in
> the Tomcat bug mentioned earlier.
>
There is no way around that. Once you have f
t; Dan Armbrust wrote:
>> >
>> > On Wed, May 26, 2010 at 12:26 PM, laredotornado
>> > >
>> > wrote:
>> >>
>> >> I tried your suggestion, and sadly it didn't work.
>> >>
>> >> What is the difference be
On Wed, May 26, 2010 at 2:18 PM, Christopher Schultz
wrote:
> Your JSP pages should be foolproof. Numeric parsing is better left to a
> servlet that can properly send the user to an error page without
> producing any output of its own.
+1 on that, and your code will be *so* much more unit-test-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kris,
On 5/26/2010 1:43 PM, Kris Schneider wrote:
> Basically, it looks like having a committed response (you've said that
> your original JSP was partially rendered) can interfere with the error
> page mechanism. For testing purposes, try increasing
, 2010 at 12:26 PM, laredotornado >
> > wrote:
> >>
> >> I tried your suggestion, and sadly it didn't work.
> >>
> >> What is the difference between what the errorPage directive does and
> what
> >> the web.xml error-page
ave
Dan Armbrust wrote:
>
> On Wed, May 26, 2010 at 12:26 PM, laredotornado
> wrote:
>>
>> I tried your suggestion, and sadly it didn't work.
>>
>> What is the difference between what the errorPage directive does and what
>> the web.xml error-page claus
t;> What is the difference between what the errorPage directive does and what
>> the web.xml error-page clause does? - Dave
>>
>>
>>
>> dcherk wrote:
>>>
>>> Dave:
>>>
>>> I believe you need a fully-qualified class name for t
On Wed, May 26, 2010 at 12:26 PM, laredotornado wrote:
>
> I tried your suggestion, and sadly it didn't work.
>
> What is the difference between what the errorPage directive does and what
> the web.xml error-page clause does? - Dave
>
I don't think this is dir
rence between what the errorPage directive does and what
> the web.xml error-page clause does? - Dave
>
>
>
> dcherk wrote:
>>
>> Dave:
>>
>> I believe you need a fully-qualified class name for the exception, eg:
>>
>> java.lang.Exception
>>
I tried your suggestion, and sadly it didn't work.
What is the difference between what the errorPage directive does and what
the web.xml error-page clause does? - Dave
dcherk wrote:
>
> Dave:
>
> I believe you need a fully-qualified class name for
Dave:
I believe you need a fully-qualified class name for the exception, eg:
java.lang.Exception
/error-pages/500.jsp
Good luck,
--
Dave Cherkassky
VP of Software Development
DJiNN Software Inc.
On 26/05/2010 10:34 AM, laredotornado wrote:
Hi,
I'm running Tomcat 6.0.26 on Mac 10.
tConnection.runIt(ChannelSocket.java:891)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
at java.lang.Thread.run(Thread.java:637)
--
View this message in context:
http://old.nabble.com/Why-does-errorPage-work-but-WEB-INF-web.xml-error-page-does-not--tp28681659p28
>> org.apache.myfaces.*
>> /web/error/Faces.jsf
>>
>>
>
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
>
n class
>> and
>> the following will not work.
>> any ideas?
>>
>>
>> org.apache.myfaces.*
>> /web/error/Faces.jsf
>>
>>
>
>
> -
> To start a new topic, e-mail:
If you need to catch a wide range of Exceptions in an error page, i
suggest you use a generic error page. The error page has access to the
Exception Object and can then include other JSP that show specific errors.
As for informations in logs file, Exceptions thrown during process of
JSF outputed u
any ideas?
org.apache.myfaces.*
/web/error/Faces.jsf
--
View this message in context:
http://www.nabble.com/web.xml-error-page-tf3805201.html#a10767952
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To s
Jon Wingfield wrote:
Have you tried the request attributes specified in section "SRV.9.9
Error Handling" of the servlet spec? Specifically, the request attribute
named "javax.servlet.error.request_uri".
No, I haven't. Thank you for your help, it works fine now.
Tomas Pop wrote:
Hello,
I
Have you tried the request attributes specified in section "SRV.9.9
Error Handling" of the servlet spec? Specifically, the request attribute
named "javax.servlet.error.request_uri".
HTH,
Jon
Tomas Pop wrote:
Hello,
I have a problem with change of the method
HttpServletRequest.getRequestUR
Hello,
I have a problem with change of the method
HttpServletRequest.getRequestURL() in Java EE 5. I have this situation:
URL matches http://server/app/page-key-word-string
These URLs generates 404 Tomcat error page, which redirects (according
to web.xml settings) to redirectServlet, where I
20 matches
Mail list logo
