This feels a little kludgy, but you can always use a signal that is
reset at some time after the activation. syncLists would then just
check that boolean signal to see if it had already been run.
Alternately, If you have a spring-style prototype scope in your
services (ie, created anew for
Make that:
onActivate(Object[] list)
{
if(params==null || params!=list) //actually a method doing a compare on
the elements of the list
{
//handle context
params = list;
}
}
Britske wrote:
>
> Thanks, removed the onActivate() without params.
>
> Moreover, i didn't test fully and
Thanks, removed the onActivate() without params.
Moreover, i didn't test fully and discovered that on a post onActivate is
called once with the context of the old page and once with the context of
the new page, so it's not always empty the first time. Probably saying the
obvious but anyway.. On
I'm not going to delve into the logic of your use case.
Just put have one activate handler:
void onActivate(Object[] context)
{
if (context.length == 0)
{
// handle no context
{
else
{
// handle context
{
}
Cheers,
Nick.
Britske wrote:
for a page, I hav
for a page, I have two activation-methods:
onActivate()
onActivate(Object[] list);
when i provide an activation context to the page both methods are called
-onactivate() first-.
This seems correct behavior according to some forum-posts i've read.
However, both methods call a method syncLists()
