You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Carlin Rogers (JIRA)" <de...@beehive.apache.org> on 2006/04/10 05:40:58 UTC

[jira] Created: (BEEHIVE-1096) Inherited NetUI shared flow reference not initialized correctly.

Inherited NetUI shared flow reference not initialized correctly.
----------------------------------------------------------------

         Key: BEEHIVE-1096
         URL: http://issues.apache.org/jira/browse/BEEHIVE-1096
     Project: Beehive
        Type: Bug

  Components: NetUI  
    Versions: 1.0.1, v.next    
    Reporter: Carlin Rogers
 Assigned to: Carlin Rogers 
     Fix For: v.next


This bug was noted in the user list.

If you have a base page flow Controller class with a declared member variable as a reference to a SharedFlowController (@Jpf.SharedFlowField annotation) and then implement a derived a page flow classs, the inherited shared flow reference field will not get initialized correctly. The base class instance is automatically intialized. However if you try to use the inherited field in the derived class it will be null.

The temporary workaround would be to explicitly declare a shared flow reference variable in the derived
Controller as well.


-- 
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-1096) Inherited NetUI shared flow reference not initialized correctly.

Posted by "Julie Zhuo (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BEEHIVE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julie Zhuo closed BEEHIVE-1096.
-------------------------------


Based on Russ' verification, close it out.

> Inherited NetUI shared flow reference not initialized correctly.
> ----------------------------------------------------------------
>
>                 Key: BEEHIVE-1096
>                 URL: https://issues.apache.org/jira/browse/BEEHIVE-1096
>             Project: Beehive
>          Issue Type: Bug
>          Components: NetUI
>    Affects Versions: 1.0.1, 1.0.2
>            Reporter: Carlin Rogers
>            Assignee: Julie Zhuo
>             Fix For: 1.0.2
>
>         Attachments: j1096-test.zip
>
>
> This bug was noted in the user list.
> If you have a base page flow Controller class with a declared member variable as a reference to a SharedFlowController (@Jpf.SharedFlowField annotation) and then implement a derived a page flow classs, the inherited shared flow reference field will not get initialized correctly. The base class instance is automatically intialized. However if you try to use the inherited field in the derived class it will be null.
> The temporary workaround would be to explicitly declare a shared flow reference variable in the derived
> Controller as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (BEEHIVE-1096) Inherited NetUI shared flow reference not initialized correctly.

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

Carlin Rogers updated BEEHIVE-1096:
-----------------------------------

    Attachment: j1096-test.zip

Test case to repro this bug. hitting the test page for the derived lass will cause an NPE.

> Inherited NetUI shared flow reference not initialized correctly.
> ----------------------------------------------------------------
>
>          Key: BEEHIVE-1096
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-1096
>      Project: Beehive
>         Type: Bug

>   Components: NetUI
>     Versions: 1.0.1, v.next
>     Reporter: Carlin Rogers
>     Assignee: Carlin Rogers
>      Fix For: v.next
>  Attachments: j1096-test.zip
>
> This bug was noted in the user list.
> If you have a base page flow Controller class with a declared member variable as a reference to a SharedFlowController (@Jpf.SharedFlowField annotation) and then implement a derived a page flow classs, the inherited shared flow reference field will not get initialized correctly. The base class instance is automatically intialized. However if you try to use the inherited field in the derived class it will be null.
> The temporary workaround would be to explicitly declare a shared flow reference variable in the derived
> Controller as well.

-- 
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] Resolved: (BEEHIVE-1096) Inherited NetUI shared flow reference not initialized correctly.

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

    Resolution: Fixed
     Assign To: Julie Zhuo  (was: Carlin Rogers)

Fixed with svn revision 418395...
http://svn.apache.org/viewvc?rev=418395&view=rev

The change includes a new test case as well.

> Inherited NetUI shared flow reference not initialized correctly.
> ----------------------------------------------------------------
>
>          Key: BEEHIVE-1096
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-1096
>      Project: Beehive
>         Type: Bug

>   Components: NetUI
>     Versions: 1.0.1, v.next
>     Reporter: Carlin Rogers
>     Assignee: Julie Zhuo
>      Fix For: v.next
>  Attachments: j1096-test.zip
>
> This bug was noted in the user list.
> If you have a base page flow Controller class with a declared member variable as a reference to a SharedFlowController (@Jpf.SharedFlowField annotation) and then implement a derived a page flow classs, the inherited shared flow reference field will not get initialized correctly. The base class instance is automatically intialized. However if you try to use the inherited field in the derived class it will be null.
> The temporary workaround would be to explicitly declare a shared flow reference variable in the derived
> Controller as well.

-- 
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-1096) Inherited NetUI shared flow reference not initialized correctly.

Posted by "Carlin Rogers (JIRA)" <de...@beehive.apache.org>.
    [ http://issues.apache.org/jira/browse/BEEHIVE-1096?page=comments#action_12421656 ] 
            
Carlin Rogers commented on BEEHIVE-1096:
----------------------------------------

The fix also includes changes from svn 422496
http://svn.apache.org/viewvc?rev=422496&view=rev

> Inherited NetUI shared flow reference not initialized correctly.
> ----------------------------------------------------------------
>
>                 Key: BEEHIVE-1096
>                 URL: http://issues.apache.org/jira/browse/BEEHIVE-1096
>             Project: Beehive
>          Issue Type: Bug
>          Components: NetUI
>    Affects Versions: 1.0.1, v.next
>            Reporter: Carlin Rogers
>         Assigned To: Julie Zhuo
>             Fix For: v.next
>
>         Attachments: j1096-test.zip
>
>
> This bug was noted in the user list.
> If you have a base page flow Controller class with a declared member variable as a reference to a SharedFlowController (@Jpf.SharedFlowField annotation) and then implement a derived a page flow classs, the inherited shared flow reference field will not get initialized correctly. The base class instance is automatically intialized. However if you try to use the inherited field in the derived class it will be null.
> The temporary workaround would be to explicitly declare a shared flow reference variable in the derived
> Controller as well.

-- 
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-1096) Inherited NetUI shared flow reference not initialized correctly.

Posted by "Russ Baker (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BEEHIVE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Russ Baker updated BEEHIVE-1096:
--------------------------------


Verified that the shared flow is not null in the derived class using Carlin's repro. Verified against SVN 549584. I recommend that this bug be closed.

> Inherited NetUI shared flow reference not initialized correctly.
> ----------------------------------------------------------------
>
>                 Key: BEEHIVE-1096
>                 URL: https://issues.apache.org/jira/browse/BEEHIVE-1096
>             Project: Beehive
>          Issue Type: Bug
>          Components: NetUI
>    Affects Versions: 1.0.1, 1.0.2
>            Reporter: Carlin Rogers
>            Assignee: Julie Zhuo
>             Fix For: 1.0.2
>
>         Attachments: j1096-test.zip
>
>
> This bug was noted in the user list.
> If you have a base page flow Controller class with a declared member variable as a reference to a SharedFlowController (@Jpf.SharedFlowField annotation) and then implement a derived a page flow classs, the inherited shared flow reference field will not get initialized correctly. The base class instance is automatically intialized. However if you try to use the inherited field in the derived class it will be null.
> The temporary workaround would be to explicitly declare a shared flow reference variable in the derived
> Controller as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.