[
https://issues.apache.org/jira/browse/SHINDIG-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700233#action_12700233
]
Adam Winer commented on SHINDIG-1015:
-------------------------------------
Patch looks good to me.
> Allow transitively-required locked-domain feature to enable locked-domain
> -------------------------------------------------------------------------
>
> Key: SHINDIG-1015
> URL: https://issues.apache.org/jira/browse/SHINDIG-1015
> Project: Shindig
> Issue Type: Improvement
> Components: Java
> Affects Versions: trunk
> Reporter: John Hjelmstad
> Assignee: John Hjelmstad
> Priority: Minor
> Fix For: trunk
>
> Attachments: SHINDIG-1015-1.patch
>
>
> At present, the only way that locked-domain is enabled is if a gadget
> explicitly includes:
> <Require feature="locked-domain"/>
> It should be possible for any particular feature, such as OpenSocial, which
> deals with sensitive information to always require locked-domain as well.
> This can be achieved by way of its dependencies (in its feature.xml):
> <dependency>locked-domain</dependency>
> The new Gadget.getAllFeatures() method makes it possible to support this.
> Patch forthcoming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
