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 no
On Wed, Sep 24, 2014 at 9:34 AM, Chris Mylonas 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 r
You should update to 5.4-beta-22
my beta-6 is like a year of betas behind! thanks
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
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
w
On Wed, Sep 24, 2014 at 8:49 AM, Chris Mylonas wrote:
> Hi Kalle,
>
>> 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
Hi Kalle,
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 gu
On Wed, Sep 24, 2014 at 5:30 AM, Chris Mylonas wrote:
>
> The SliderSectionServiceImpl throws higher up the stack - can this pass
>>> the exception up to setupRender? I thought "throws SystemException" would
>>> have been enough?
>>>
>>
>> What about having your code handling the exceptions its
The SliderSectionServiceImpl throws higher up the stack - can this pass
the exception up to setupRender? I thought "throws SystemException"
would have been enough?
What about having your code handling the exceptions itself, when it
calls the EJB methods that can throw exceptions?
Han
On Wed, 24 Sep 2014 05:57:05 -0300, Chris Mylonas
wrote:
Here's the log, sorry for omission - long day.
The SliderSectionServiceImpl throws higher up the stack - can this pass
the exception up to setupRender? I thought "throws SystemException"
would have been enough?
What about having
Here's the log, sorry for omission - long day.
The SliderSectionServiceImpl throws higher up the stack - can this pass
the exception up to setupRender? I thought "throws SystemException" would
have been enough?
Chris
[#|2014-09-24T17:12:32.253+1000|WARNING|glassfish3.1.2|javax.enterpris
Hi Tapestry Users,
Short version: Can a component use @InjectPage to redirect in case there
is a problem during the render phase?
Unabridged version:
I have a my business layers running EJB.
Layout of project is like jumpstart for EJB stuff. Works great.
EJB can't find any values in the d
11 matches
Mail list logo