What I do is override the ExceptionPresenter service. My own implementation
somehow reads a system property, then redirects to either a custom generic
page or the standard tapestry exception page depending on the environment
(dev or prod).
2007/4/29, Jesse Kuhnert <[EMAIL PROTECTED]>:
Thanks wi
Thanks will fix.
On 4/28/07, Martin Strand <[EMAIL PROTECTED]> wrote:
That page says "tapestry.Infrastructure", it should be
"tapestry.InfrastructureOverrides"
Martin
On Sun, 29 Apr 2007 04:44:19 +0200, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
> Right. For more on the hivemind specifics only
That page says "tapestry.Infrastructure", it should be
"tapestry.InfrastructureOverrides"
Martin
On Sun, 29 Apr 2007 04:44:19 +0200, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
Right. For more on the hivemind specifics only see:
http://tapestry.apache.org/tapestry4.1/developmentguide/except
Right. For more on the hivemind specifics only see:
http://tapestry.apache.org/tapestry4.1/developmentguide/exceptionpages.html
On 4/27/07, jake123 <[EMAIL PROTECTED]> wrote:
Hi Josh,
you can do a infrastructur override in your hivemodule.xml like this:
and then you create yo
Hi Josh,
you can do a infrastructur override in your hivemodule.xml like this:
and then you create your own CustomExceptionPage:
public abstract class CustomExceptionPage extends Exception implements
PageDetachListener {
private static Logger log =
LoggerFactory.getLogger(Custom
The absolute easiest thing to do is to create a page named Exception
(.html and .page). This will then be picked up automatically as the
Exception page. Unfortunately you may have to do some build script
magic to differentiate between production and development. I have my
production Exceptio
