But in addition our exception handler extracts redirect destination from
our custom exception and performs redirect.
16.01.2014 17:08 пользователь "Thiago H de Paula Figueiredo" <
thiag...@gmail.com> написал:
> On Thu, 16 Jan 2014 10:41:55 -0200, Andrey wrote:
>
> Finally we've solved spam probl
On Thu, 16 Jan 2014 10:41:55 -0200, Andrey wrote:
Finally we've solved spam problem (but my collegues are not very happy
with
this entire approach):
we use log4j matcher to skip error log message from RenderQueueImpl, and
log it if needed in our exception handler.
p.s. getters do not help, b
data
unavailable.
page request check looks better but, imho, code would become much harder to
understand and support.
2014/1/16 Thiago H de Paula Figueiredo
> On Thu, 16 Jan 2014 05:49:09 -0200, Andrey wrote:
>
> Hello!
>>
>
> Hi!
>
>
> We are in need of redirect fr
This may help:
http://jumpstart.doublenegative.com.au/jumpstart/examples/infrastructure/handlingabadcontext/1
Geoff
On 16/01/2014, at 6:49 PM, Andrey wrote:
> Hello!
>
> We are in need of redirect from render phase.
> Reasons are: we cannot fetch all required data i
On Thu, 16 Jan 2014 05:49:09 -0200, Andrey wrote:
Hello!
Hi!
We are in need of redirect from render phase.
Reasons are: we cannot fetch all required data in onActivate method of
page, because onActivate is called for page even for component events
inside page.
So we load data in
Hello!
We are in need of redirect from render phase.
Reasons are: we cannot fetch all required data in onActivate method of
page, because onActivate is called for page even for component events
inside page.
So we load data in setupRender. But there can be problems like data not
found, service