You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <de...@beehive.apache.org> on 2005/10/19 21:08:45 UTC

[jira] Created: (BEEHIVE-978) Shared flows are shared across target scopes

Shared flows are shared across target scopes
--------------------------------------------

         Key: BEEHIVE-978
         URL: http://issues.apache.org/jira/browse/BEEHIVE-978
     Project: Beehive
        Type: Bug
  Components: NetUI  
    Versions: V1    
    Reporter: Rich Feit
 Assigned to: Rich Feit 
     Fix For: 1.1


"Target scopes" are a way of separating a set of page flow instances in the session, so they don't interfere with each other.  This is useful with multiple browser frames/windows, or with portlets.  A target scope is addressed using the "targetScope" attribute in the NetUI tags, or by adding the "jpfScopeID=..." parameter to the URL.

Currently, a shared flow instance is shared across all target scopes.  To see this, hit /pageFlowCore/sharedFlowScoping/frames.html in the attached repro case, and submit a value in one of the frames.  Then click refresh in the other frame -- you'll see the same value, when really it should still be blank.

-- 
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


[jira] Commented: (BEEHIVE-978) Shared flows are shared across target scopes

Posted by "Rich Feit (JIRA)" <de...@beehive.apache.org>.
    [ http://issues.apache.org/jira/browse/BEEHIVE-978?page=comments#action_12332520 ] 

Rich Feit commented on BEEHIVE-978:
-----------------------------------

The automated test is SharedFlowScoping in the NetUI BVT suite.

> Shared flows are shared across target scopes
> --------------------------------------------
>
>          Key: BEEHIVE-978
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-978
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Rich Feit
>      Fix For: 1.1
>  Attachments: j978-repro.zip
>
> "Target scopes" are a way of separating a set of page flow instances in the session, so they don't interfere with each other.  This is useful with multiple browser frames/windows, or with portlets.  A target scope is addressed using the "targetScope" attribute in the NetUI tags, or by adding the "jpfScopeID=..." parameter to the URL.
> Currently, a shared flow instance is shared across all target scopes.  To see this, hit /pageFlowCore/sharedFlowScoping/frames.html in the attached repro case, and submit a value in one of the frames.  Then click refresh in the other frame -- you'll see the same value, when really it should still be blank.

-- 
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


[jira] Updated: (BEEHIVE-978) Shared flows are shared across target scopes

Posted by "Rich Feit (JIRA)" <de...@beehive.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-978?page=all ]

Rich Feit updated BEEHIVE-978:
------------------------------

    Attachment: j978-repro.zip

repro

> Shared flows are shared across target scopes
> --------------------------------------------
>
>          Key: BEEHIVE-978
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-978
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Rich Feit
>     Assignee: Rich Feit
>      Fix For: 1.1
>  Attachments: j978-repro.zip
>
> "Target scopes" are a way of separating a set of page flow instances in the session, so they don't interfere with each other.  This is useful with multiple browser frames/windows, or with portlets.  A target scope is addressed using the "targetScope" attribute in the NetUI tags, or by adding the "jpfScopeID=..." parameter to the URL.
> Currently, a shared flow instance is shared across all target scopes.  To see this, hit /pageFlowCore/sharedFlowScoping/frames.html in the attached repro case, and submit a value in one of the frames.  Then click refresh in the other frame -- you'll see the same value, when really it should still be blank.

-- 
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


[jira] Closed: (BEEHIVE-978) Shared flows are shared across target scopes

Posted by "Rich Feit (JIRA)" <de...@beehive.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-978?page=all ]
     
Rich Feit closed BEEHIVE-978:
-----------------------------

    Resolution: Fixed
     Assign To:     (was: Rich Feit)

Fixed with revision 326660.  I added an automated test for this -- closing.

> Shared flows are shared across target scopes
> --------------------------------------------
>
>          Key: BEEHIVE-978
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-978
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Rich Feit
>      Fix For: 1.1
>  Attachments: j978-repro.zip
>
> "Target scopes" are a way of separating a set of page flow instances in the session, so they don't interfere with each other.  This is useful with multiple browser frames/windows, or with portlets.  A target scope is addressed using the "targetScope" attribute in the NetUI tags, or by adding the "jpfScopeID=..." parameter to the URL.
> Currently, a shared flow instance is shared across all target scopes.  To see this, hit /pageFlowCore/sharedFlowScoping/frames.html in the attached repro case, and submit a value in one of the frames.  Then click refresh in the other frame -- you'll see the same value, when really it should still be blank.

-- 
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