You should be able to contribute your override of RequestExceptionHandle to the tapestry.InfrastructureOverrides service configuration .... I just haven't implemented that yet!
The name of the page is "core/ExceptionReport". If you create a page in your application named "ExceptionReport", Tapestry should favor that over the default one in the core library. You page must implement the ExceptionReporter interface. On 2/22/07, Ted Steen <[EMAIL PROTECTED]> wrote:
and I guess that I should contribute a ExceptionReporter page and not a RequestExceptionHandler, but I just cant find out where. 2007/2/22, Ted Steen <[EMAIL PROTECTED]>: > Again with the questions... > > Is the exception page pluggable yet? If so, where should it be contributed? > I couldnt find it out by looking att the T5 source. > > If I try to contribute RequestExceptionHandler to the infrastructure > with the name > RequestExceptionHandler" tapestry says > > "Contribution <Proxy for > peng5.Peng5RequestExceptionHandler(org.apache.tapestry.services.RequestExceptionHandler)> > (as 'RequestExceptionHandler') duplicates existing contribution <Proxy > for tapestry.internal.DefaultRequestExceptionHandler(org.apache.tapestry.services.RequestExceptionHandler)> > and has been ignored." > > > -- > /ted > -- /ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
