I would say no.
The behavior in production.and development mode differences in general is a bad
idea. This will preclude valid testing in development.
On Jul 31, 2013, at 10:51 AM, Howard Lewis Ship <hls...@gmail.com> wrote:
> Could this be a case where we want one behavior in development (a Tapestry
> error) and another in production (a 404 status)?
>
>
> On Wed, Jul 31, 2013 at 8:38 AM, Dimitris Zenios
> <dimitris.zen...@gmail.com>wrote:
>
>> +1
>>
>>
>> On Wed, Jul 31, 2013 at 6:21 PM, Lenny Primak <lpri...@hope.nyc.ny.us
>>> wrote:
>>
>>> Big +1 for me. I currently use the following code in the index page to
>>> work around this issue:
>>>
>>> 8 /**
>>> 9 * Restore 404 Not Found errors
>>> 10 * @param context
>>> 11 * @return
>>> 12 */
>>> 13 HttpError onActivate(EventContext context)
>>> 14 {
>>> 15 if (context.getCount() == 0)
>>> 16 {
>>> 17 return null;
>>> 18 }
>>> 19
>>> 20 return new HttpError(404, "Resource not found.");
>>> 21 }
>>>
>>>
>>> On Jul 31, 2013, at 10:14 AM, Massimo Lusetti <mluse...@gmail.com>
>> wrote:
>>>
>>>> Hi devs,
>>>> I would like to have
>>>> https://issues.apache.org/jira/browse/TAP5-2070closed before 5.4 will
>>>> go to beta stage.
>>>>
>>>> I mainly want to decide if the current behavior is acceptable for the
>>>> majority or we need to change it, then we can discuss on the
>>> implementation.
>>>>
>>>> Please comment.
>>>>
>>>> --
>>>> Massimo Lusetti
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
