[ http://issues.apache.org/jira/browse/BEEHIVE-789?page=all ]
Alejandro Ramirez updated BEEHIVE-789:
--------------------------------------
Component: NetUI
(was: Samples)
Description:
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.
was:
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.
Assign To: Julie Zhuo (was: David Read)
Updated component from Samples to Netui. Also re-assigned to Julie for
verification
> PageFlowEventReporter.flowControllerDestroyed() does not expose the SessionID
> -----------------------------------------------------------------------------
>
> Key: BEEHIVE-789
> URL: http://issues.apache.org/jira/browse/BEEHIVE-789
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
