I'm going to have to d/l your project and go over it more carefully than a
browser look at it. The error I omitted when using
RequestExceptionHandler was, sic, "there is no such service by that name".
However, that was >midnight and this morning when I tried it deployed.
Unfortunately it did not redirect as I thought it would and I have since
done:
void setupRender() {
// slider = sliderService.getById(new Long(1)); //using the EJB
through an @Inject T5 service
// slider = sliderEJBService.getById(new Long(1)); //using the @EJB
notation
throw new SliderException(new Throwable("YEAH")); //just throw an
exception
}
But I'm getting the standard exception report page. This is on beta-6
because I can't get beta-22 to work (see other thread re: commons-io
dependency)
An exception has occurred processing this request.
Render queue error in SetupRender[Index:layout.slider]:
java.lang.Throwable: YEAH
I might go back to my prototyping workflow using tapestry-hibernate so
there is less "other shit" in the way when doing the tapestry stuff because
it'll be quicker. (Might give me a chance to write some codegen scripts)
P.S. Thiago, if you read this, mail died a couple of times today and rss
feeds didn't update correctly without a shutdown. I'll reboot my machine,
but this is unix underneath man! 21st century too! :P
On Thu, Sep 25, 2014 at 9:09 AM, Kalle Korhonen <[email protected]>
wrote:
> On Wed, Sep 24, 2014 at 9:34 AM, Chris Mylonas <[email protected]> wrote:
>
> >
> >> In 5.4, you can contribute to the default error page and map exception
> >> types to specific error pages (
> >> http://tapestry.apache.org/5.4/apidocs/org/apache/
> >> tapestry5/internal/services/DefaultRequestExceptionHandler.html
> >> - that reminds me, I should add information about that to the user guide
> >> as
> >> well).
> >>
> >
> > And I've contributed all this in AppModule
> > public void
> contributeDefaultRequestExceptionHandler(MappedConfiguration<Class,
> > Class> configuration) {
> > configuration.add(SliderException.class, DefaultNeeded.class);
> > }
> >
> > with a few attempts guessing the method name
> contributeRequestExceptionHandler,
> > contributeExceptionHandler but each time a similar error in the logs:
> > Caused by: java.lang.IllegalArgumentException: Contribution
> > org.opencsta.website.metwide.web.services.AppModule.
> > contributeDefaultRequestExceptionHandler(MappedConfiguration) (at
> > AppModule.java:133) is for service 'DefaultRequestExceptionHandler',
> > which does not exist.
> >
>
> RequestExceptionHandler is the interface and the service name, so
> contributeRequestExceptionHandler works, I wonder which error message you
> got when you tried it. DefaultRequestExceptionHandler is the default
> exceptionHandler that accepts contributions. This configuration is already
> being used in tapestry-security 0.6, which is for T5.4 (see
>
> https://github.com/tynamo/tapestry-security/blob/master/src/main/java/org/tynamo/security/services/SecurityModule.java
> ).
>
> Kalle
>
