Announcement Announcement Module
Collapse
No announcement yet.
What happened to FlexSessionListener and FlexClientListener after RC1? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • What happened to FlexSessionListener and FlexClientListener after RC1?

    Hi,
    Is there a new way to register for notifications on session destroyed, client destroyed?
    Registering the following in the config processor doesn't trigger any notifications.
    FlexSession.addSessionCreatedListener(sessionListe ner);
    FlexClient.addClientCreatedListener(clientListener );
    MessageClient.addMessageClientCreatedListener(mess ageClientListener);

    They worked in M2. Actually, if I ommit to include the xalan.jar in the classpath and the integration doesn't start correctly, I get the notifications.

    How can I get notified when client or session were destroyed?

    Thanks

  • #2
    I can't think of anything we changed after M2 that would be causing such a change in behavior. You do have the HttpFlexSession registered as a listener in web.xml, right? If you're certain you've got things configured correctly and this is consistently reproducible, please open a Jira with the steps to reproduce.

    Comment

    Working...
    X