You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Ryan Baxter (JIRA)" <ji...@apache.org> on 2011/03/04 16:34:37 UTC

[jira] Created: (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

Allow extensions to the common container by allowing other features to provide their own namespace
--------------------------------------------------------------------------------------------------

                 Key: SHINDIG-1513
                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
             Project: Shindig
          Issue Type: Improvement
          Components: Java
    Affects Versions: 3.0.0
            Reporter: Ryan Baxter
            Priority: Minor
             Fix For: 3.0.0


At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

Posted by "Paul Lindner (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SHINDIG-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Lindner closed SHINDIG-1513.
---------------------------------


part of 2.5.0-beta1 release.

                
> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 2.5.0-beta1
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 2.5.0-beta1
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

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

Ryan Baxter updated SHINDIG-1513:
---------------------------------

    Attachment: fix-1513.patch

> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

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

Ryan Baxter updated SHINDIG-1513:
---------------------------------

    Attachment:     (was: fix-1513.patch)

> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

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

Ryan Baxter updated SHINDIG-1513:
---------------------------------

    Attachment: fix-1513.patch

> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

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

Ryan Baxter updated SHINDIG-1513:
---------------------------------

    Attachment: fix-1513.patch

> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

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

Paul Lindner resolved SHINDIG-1513.
-----------------------------------

    Resolution: Fixed

committed Mar 9.


> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SHINDIG-1513) Allow extensions to the common container by allowing other features to provide their own namespace

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

Ryan Baxter updated SHINDIG-1513:
---------------------------------

    Attachment:     (was: fix-1513.patch)

> Allow extensions to the common container by allowing other features to provide their own namespace
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1513
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1513
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 3.0.0
>            Reporter: Ryan Baxter
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: fix-1513.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At the moment the common container cannot be extended by adding a new namespace and still have access to the container object.  The only reasonable way to extend the common container at this moment it to add new methods by calling .prototype or by subclassing it.  Another useful extension would be to allow features to add their own namespace to the common container and add new methods under that common container.  However those methods may still want to reference other methods inside the common container so they need to be able to access the common container object itself.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira