[
https://jira.jboss.org/browse/SEAMREMOTING-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559530#action_12559530
]
Shane Bryzak commented on SEAMREMOTING-16:
------------------------------------------
Still a valid issue for Seam 3
> constraint by inclusion on remote calls object fields
> -----------------------------------------------------
>
> Key: SEAMREMOTING-16
> URL: https://jira.jboss.org/browse/SEAMREMOTING-16
> Project: Seam Remoting
> Issue Type: Feature Request
> Reporter: Zalder R
> Assignee: Shane Bryzak
> Priority: Optional
>
> I think it could be nice to define the fields of the objects returned in a
> "WebRemote call" with an "include" parameter (instead of the current exclude
> parameter).
> For instance :
> now you have :
> @WebRemote(exclude = {"secret"})
> it would be nice to be able to define :
> @WebRemote(include = {"fieldIreallyNeed1", "fieldIreallyNeed2"})
> The reasons for this are many :
> - security : if the object structure varies over time, you would not want the
> new fields to be available on the client side by default
> - in some cases it's a lot more lightweight (both in the code and in the
> volume of data sent) to define a minimum set of fields you want instead of
> the fields you don't want
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
