Return-Path: X-Original-To: apmail-shindig-issues-archive@www.apache.org Delivered-To: apmail-shindig-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F7F29A57 for ; Mon, 18 Jun 2012 09:34:30 +0000 (UTC) Received: (qmail 6274 invoked by uid 500); 18 Jun 2012 09:26:06 -0000 Delivered-To: apmail-shindig-issues-archive@shindig.apache.org Received: (qmail 5569 invoked by uid 500); 18 Jun 2012 09:25:53 -0000 Mailing-List: contact issues-help@shindig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shindig.apache.org Delivered-To: mailing list issues@shindig.apache.org Received: (qmail 5184 invoked by uid 99); 18 Jun 2012 09:25:43 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 09:25:43 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 4A22A142868 for ; Mon, 18 Jun 2012 09:25:43 +0000 (UTC) Date: Mon, 18 Jun 2012 09:25:43 +0000 (UTC) From: "Erik BI (JIRA)" To: issues@shindig.apache.org Message-ID: <857514364.24210.1340011543305.JavaMail.jiratomcat@issues-vm> In-Reply-To: <573975055.53006.1313763507415.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (SHINDIG-1588) Variable substitution should support EL syntax MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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