You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Ted Steen <te...@gmail.com> on 2007/02/22 15:53:40 UTC
T5: contributing own ExceptionReporter
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5: contributing own ExceptionReporter
Posted by Howard Lewis Ship <hl...@gmail.com>.
Also, this stuff is likely to change; even for reporting exceptions,
an action request should be followed by a render request. I've been
holding off on that change until I implement a "client" persistence
strategy.
On 2/22/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> 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 <te...@gmail.com> 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 <te...@gmail.com>:
> > > 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: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> 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
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5: contributing own ExceptionReporter
Posted by Howard Lewis Ship <hl...@gmail.com>.
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 <te...@gmail.com> 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 <te...@gmail.com>:
> > 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: T5: contributing own ExceptionReporter
Posted by Ted Steen <te...@gmail.com>.
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 <te...@gmail.com>:
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org