shindig-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik BI (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SHINDIG-1588) Variable substitution should support EL syntax
Date Mon, 18 Jun 2012 09:25:43 GMT

    [ https://issues.apache.org/jira/browse/SHINDIG-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395764#comment-13395764
] 

Erik BI commented on SHINDIG-1588:
----------------------------------

Hi Ryan, I saw something in the spec and would like to confirm with you. 

In the spec, it states all variables are stored in DataContext: 

9.2 Variables

All variables are stored in the DataContext (Section 14.1).

and in 14.1, it says the Data in Data Context is only available in 3 contexts. 

14.1 DataContext
......
Data in the Data Context is available in three contexts:

    Proxied content requests. This data will be POSTed to the developer party server with
requests for proxied content.
    OpenSocial Templates. The data will be available as named variables in OpenSocial templates.
    JavaScript. This data will be available in the JavaScript API.

I checked the Shindig code and in template it has already support the EL syntax, so what's
the support this issue is talking about? 
                
> Variable substitution should support EL syntax
> ----------------------------------------------
>
>                 Key: SHINDIG-1588
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1588
>             Project: Shindig
>          Issue Type: Bug
>    Affects Versions: 2.5.0-beta1
>            Reporter: Ryan Baxter
>              Labels: opensocial_specification_compliance
>
> The OpenSocial 2.0 specification now states that the old way of doing variable subsitution
is now deprecated in favor of using EL syntax.  We should add that support to Shindig as well.
> http://opensocial-resources.googlecode.com/svn/spec/2.0/Core-Gadget.xml#rfc.section.9.4

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

        

Mime
View raw message