Hello
The previous solution is based on the same idea than returning a
javax.net.URL or Tapestry Link, i'm not sure this is the best thing to do
but it works.
Regards,
Christophe.
2009/10/12 cordenier christophe
> 1. Create a class ErrorCode that will handle the error status and error
> message
1. Create a class ErrorCode that will handle the error status and error
message
2. Implement an ErrorCodeResultProcessor
public class ErrorCodeResultProcessor implements
ComponentEventResultProcessor {
private final Response response;
public ErrorCodeResultProcess
On Wed, Oct 7, 2009 at 9:17 AM, cordenier christophe
wrote:
> Thanks, but i didn't look that way because of what found in the Tapestry
> documentation. I mean 'vestigal' like deprecated :)
> I will have a try.
> tapestry.start-page-name The logical name of the start page, the page that
> is render
Thanks, but i didn't look that way because of what found in the Tapestry
documentation. I mean 'vestigal' like deprecated :)
I will have a try.
tapestry.start-page-name The logical name of the start page, the page that
is rendered for the *root URL*. This is normally "start". This functionality
is
On Wed, Oct 7, 2009 at 1:24 AM, cordenier christophe
wrote:
> Does it mean that since we have an index page in our application, 404 will
> never be thrown automatically ?
There's a different between Start and Index page. Start page handles a
request to context path only, but Index handles is sort
Sorry for my last post i answered to fast... I think this won't be useful
since you do not have access to 'Tapestry request parameters' in this kind
of filter. Moreover IgnoredPathsFilter already have a filter mechanism based
on patterns.
2009/10/7 Jan Jirout
> Hi again,
>
> thanks for help. I h
Have a look at the IgnoredPathsFilter implementation.
If you define your own HttpServletRequestFilter to avoid handling some URLs,
i think this could be good workaround to your problem. Returning false will
let the request go through and the automatically let Tomcat send 404 error.
2009/10/7 Jan
Hi again,
thanks for help. I have look at bug report that you have entered (https://issues.apache.org/jira/browse/TAP5-879
).
I have tested it. When I don't have "onActivate" method in my
Index.java file and user tries access not existing page then Index is
normally shown. Maybe it could b
/email.html for important
additional terms relating to this e-mail.
- Original Message -
From: "cordenier christophe"
To: "Tapestry users"
Sent: Wednesday, 7 October, 2009 16:44:17 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Problem with error404
Thanks
Thanks, I did it.
2009/10/7 Thiago H. de Paula Figueiredo
> Em Wed, 07 Oct 2009 10:17:09 -0300, Robin Komiwes
> escreveu:
>
> I must agree with Christophe. With the current behavior, you are not able
>> to distinguish a page that doesn't exist.
>>
>
> Please post a JIRA about it.
>
> --
> Thia
Em Wed, 07 Oct 2009 10:17:09 -0300, Robin Komiwes
escreveu:
I must agree with Christophe. With the current behavior, you are not
able to distinguish a page that doesn't exist.
Please post a JIRA about it.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instruc
I must agree with Christophe. With the current behavior, you are not able to
distinguish a page that doesn't exist.
This is awkward because being aware of incorrect pages access is common
request from professionals customers.
On Wed, Oct 7, 2009 at 2:27 PM, cordenier christophe <
christophe.corde
I agree, but i think this behaviour 'should' be avoid if the index has not
an activation method with the corresponding parameter length and type... A
404 should be automatically raised for this kind of request.
2009/10/7 Jan Jirout
> Hi,
>
> It seems that it works like this. If you access not ex
Hi,
It seems that it works like this. If you access not existing page http://localhost/demo/bla
it's translated in to http://localhost/demo/index/blah. I think that
it's default behavior.
Jan
On Oct 7, 2009, at 10:24 AM, cordenier christophe wrote:
Hi
From my humble point of view, usin
Hi
>From my humble point of view, using the activate method to send an error
when page doesn't exist is not the right place. Imagine that you have
subpackage with there own index page, you will have to duplicate your code.
But your question is really pertinent, and I had a closer look at the
Comp
Don't think I can help you much, but I can verify the same sendError
and error configurations work for me on Tomcat 5.5 (haven't tried on
Tomcat 6).
Kalle
On Tue, Oct 6, 2009 at 3:05 AM, Jan Jirout wrote:
> Hi All,
>
> I'm playing some time with t5. I have meet simple problem. I hope that it's
Hi,
Thanks for reply. It seems to me like work around. You suppose me to
change place where I detect that page can't be found to different
one. When I place this logic of detecting invalid page in filer then
I'll do this work two times. Once time in filter and second time I'll
examine th
Hello
Have you tried with a ComponenRequestFilter instead ?
Christophe
2009/10/6 Jan Jirout
> Hi All,
>
> I'm playing some time with t5. I have meet simple problem. I hope that it's
> not my fault.
>
> So.
>
> I would like to handle "Error 404" in my application so I have in web.xml:
>
>
Hi All,
I'm playing some time with t5. I have meet simple problem. I hope that
it's not my fault.
So.
I would like to handle "Error 404" in my application so I have in
web.xml:
app
/*
REQUEST
ERROR
19 matches
Mail list logo
