[
https://issues.apache.org/jira/browse/SHINDIG-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278226#comment-13278226
]
[email protected] commented on SHINDIG-1779:
--------------------------------------------------------
bq. On 2012-05-17 13:38:17, Ryan Baxter wrote:
bq. > Erik, I am not sure I understand the need for this change. Could you
explain or provide a concrete example which demonstrates the need for this?
Erik please see my comment above, can you give us a concrete use case for these
changes?
- Ryan
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/5134/#review7957
-----------------------------------------------------------
On 2012-05-17 14:19:41, Erik Bi wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/5134/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-05-17 14:19:41)
bq.
bq.
bq. Review request for Ryan Baxter, Dan Dumont and Stanton Sievers.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. There are requirements to expose some specific attributes in the feed
result. These attributes are not specific to any entry i.e. global in scope.
for example, it is possible that user may require additional attributes to be
passed like "Configuration parameters used by the front end to present Activity
entries"
bq. Would like the RestfulCollection object to be backed by a map with the put
and get methods exposed, similar to how ActivityEntry and ActivityObject are
currently handled.
bq.
bq.
bq. This addresses bug shindig-1779.
bq. https://issues.apache.org/jira/browse/shindig-1779
bq.
bq.
bq. Diffs
bq. -----
bq.
bq.
http://svn.apache.org/repos/asf/shindig/trunk/java/common/src/main/java/org/apache/shindig/protocol/conversion/BeanXStreamConverter.java
1327432
bq.
http://svn.apache.org/repos/asf/shindig/trunk/java/social-api/src/main/java/org/apache/shindig/social/core/util/atom/AtomFeed.java
1339014
bq.
http://svn.apache.org/repos/asf/shindig/trunk/java/common/src/main/java/org/apache/shindig/common/JsonSerializer.java
1327432
bq.
http://svn.apache.org/repos/asf/shindig/trunk/java/common/src/main/java/org/apache/shindig/protocol/RestfulCollection.java
1339011
bq.
bq. Diff: https://reviews.apache.org/r/5134/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Erik
bq.
bq.
> Make RestfulCollection object to be backed by a map with the put and get
> methods exposed
> ----------------------------------------------------------------------------------------
>
> Key: SHINDIG-1779
> URL: https://issues.apache.org/jira/browse/SHINDIG-1779
> Project: Shindig
> Issue Type: New Feature
> Components: Java
> Affects Versions: 2.5.0
> Reporter: Erik BI
> Fix For: 2.5.0
>
>
> There are requirements to expose some specific attributes in the feed result.
> These attributes are not specific to any entry i.e. global in scope. for
> example, it is possible that user may require additional attributes to be
> passed like "Configuration parameters used by the front end to present
> Activity entries"
> Would like the RestfulCollection object to be backed by a map with the put
> and get methods exposed, similar to how ActivityEntry and ActivityObject are
> currently handled.
--
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