beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julie Zhuo (JIRA)" <>
Subject [jira] Closed: (BEEHIVE-789) PageFlowEventReporter.flowControllerDestroyed() does not expose the SessionID
Date Fri, 02 Sep 2005 04:44:13 GMT
     [ ]
Julie Zhuo closed BEEHIVE-789:

Verified at rev265606.  The API how has a seesion Object in its signature.
flowControllerDestroyed(FlowController flowController, Object storageLocation). The following
is actual log the DefaultPageFlowEventReporter produced,

01 Sep 2005 22:35:36,967 DEBUG DefaultPageFlowEventReporter []: flowControllerDestroyed: FlowControll
er=jira786.Controller@3e5a91, StorageLocation=org.apache.catalina.session.StandardSessionFacade@1408a75

> PageFlowEventReporter.flowControllerDestroyed() does not expose the SessionID
> -----------------------------------------------------------------------------
>          Key: BEEHIVE-789
>          URL:
>      Project: Beehive
>         Type: Improvement
>   Components: NetUI
>     Versions: v1m1
>  Environment: Windows XP
>     Reporter: David Read
>     Assignee: Julie Zhuo
>     Priority: Minor
>      Fix For: V1

> If you want to track the lifetime of PageFlows, you might need to "see" the HTTP Session
ID when the flow is destroyed.  Currently, the API only includes the flowController, and there's
no public API to get the Session ID from the flowController.
> void flowControllerDestroyed( FlowController flowController );
> Note that having the request object (as a way to get the Session ID) probabaly wouldn't
help here since the flow can be destroyed outside the context of a request (e.g. HTTP Session
timeout).  It's probably more useful to have the ID exposed as part of the API.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message