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 2012/06/15 20:39:42 UTC

[jira] [Created] (SHINDIG-1802) We handle invalid EE data model target types incorrectly in the EE container code

Ryan Baxter created SHINDIG-1802:
------------------------------------

             Summary: We handle invalid EE data model target types incorrectly in the EE container code
                 Key: SHINDIG-1802
                 URL: https://issues.apache.org/jira/browse/SHINDIG-1802
             Project: Shindig
          Issue Type: Bug
    Affects Versions: 2.5.0
            Reporter: Ryan Baxter
            Assignee: Ryan Baxter




--
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] [Resolved] (SHINDIG-1802) We handle invalid EE data model target types incorrectly in the EE container code

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

Ryan Baxter resolved SHINDIG-1802.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.0

Committed revision 1351771
                
> We handle invalid EE data model target types incorrectly in the EE container code
> ---------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1802
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1802
>             Project: Shindig
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Ryan Baxter
>            Assignee: Ryan Baxter
>             Fix For: 2.5.0
>
>         Attachments: issue-1802.patch
>
>
> If an EE data model only has a URL and specifies a target type of gadget in its preferred experience the EE container code will still try to render a gadget.  According to the spec if a data model specifies a target type that the data model does not contain than the container should ignore the target type.
> http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#rfc.section.C.15.3.2

--
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-1802) We handle invalid EE data model target types incorrectly in the EE container code

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

Ryan Baxter updated SHINDIG-1802:
---------------------------------

    Attachment: issue-1802.patch
    
> We handle invalid EE data model target types incorrectly in the EE container code
> ---------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1802
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1802
>             Project: Shindig
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Ryan Baxter
>            Assignee: Ryan Baxter
>         Attachments: issue-1802.patch
>
>
> If an EE data model only has a URL and specifies a target type of gadget in its preferred experience the EE container code will still try to render a gadget.  According to the spec if a data model specifies a target type that the data model does not contain than the container should ignore the target type.
> http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#rfc.section.C.15.3.2

--
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-1802) We handle invalid EE data model target types incorrectly in the EE container code

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

Ryan Baxter updated SHINDIG-1802:
---------------------------------

    Description: 
If an EE data model only has a URL and specifies a target type of gadget in its preferred experience the EE container code will still try to render a gadget.  According to the spec if a data model specifies a target type that the data model does not contain than the container should ignore the target type.
http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#rfc.section.C.15.3.2
    
> We handle invalid EE data model target types incorrectly in the EE container code
> ---------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1802
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1802
>             Project: Shindig
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Ryan Baxter
>            Assignee: Ryan Baxter
>
> If an EE data model only has a URL and specifies a target type of gadget in its preferred experience the EE container code will still try to render a gadget.  According to the spec if a data model specifies a target type that the data model does not contain than the container should ignore the target type.
> http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-Gadget.xml#rfc.section.C.15.3.2

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