Skip to main content
F
Flammenmensch
Participating Frequently
April 26, 2011
Question

Cairngorm 3 NavigationParsley [Enter] and [Init] handlers

  • April 26, 2011
  • 1 reply
  • 3169 views

Hi,

It looks like after recent updates to NavigationParsley library Navigation's [Enter] handlers are executed before Parsley's [Init] handlers.

Is it an intended behaviour now?

This topic has been closed for replies.

1 reply

A
Alex Uhlmann
Participating Frequently
April 26, 2011

Interesting, I would have expected this to also happen in earlier releases. Are you sure nothing else in the initialization of your module/deferred component has changed? Only the very latest release of the nav lib contains a feature that prevents this to happen. Check out https://bugs.adobe.com/jira/browse/CGM-68

So with this feature, the module lib also should work better with the nav lib.

I've attached a snapshot release of the 1.5 version. Let me know if you get the chance to test it. That said, this version only works with Parsley 2.4 and we don't apply features to older versions of IoC frameworks once we migrated so hope that's ok in your case.

Cheers,

Alex

F
FlammenmenschAuthor
Participating Frequently
April 27, 2011

Alex,

I'm sure that nothing was changed in my presentation components. Today I switched to Parsley 2.4 and updated NavigationParsley library to the latest revision (I'm using trunk version in my application). I also checked the attached snapshot lib and the issue appeared under both versions.

By the way, after I switched to Parsley 2.4 I noticed a stranged behaviour of MessageInterceptor. It seems that [MessageInterceptor] handlers are executed after [MessageHandler] methods by default. Adding order="1" attribute to MessageInterceptor tags fixes the problem.

As far as I know NavigationLibrary for Parsley uses message interceptors which were changed in version 2.4. Maybe this is connected somehow with this issue?

A
Alex Uhlmann
Participating Frequently
April 27, 2011

Yes, the nav lib does use the new message interceptor implementation of Parsley 2.4 but only for it's own navigation events. I cannot see how it should interfere with the out of the box 2.4 message interceptor feature. Or are you intercepting the nav event  also with a message interceptor additionally?  Note, MessageInterceptor object definition is now deprecated in 2.4 so  you would need to use MessageHandler with a new arguments. Check he 2.4 docs for it. Maybe the legacy MessageInterceptor doesn't work together witht he new one; but you better ask that in the Parsley forum. But in any way, probably better to just migrate your code to the new syntax.

About the Nav lib issue, any chance you can send me something isolated? Can you reprodce this in any of the NavigationParsleyTest samples?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices