[
https://jira.jboss.org/browse/SEAMREMOTING-16?page=com.atlassian.jira.plu...
]
Shane Bryzak moved JBSEAM-975 to SEAMREMOTING-16:
-------------------------------------------------
Project: Seam Remoting (was: Seam)
Key: SEAMREMOTING-16 (was: JBSEAM-975)
Component/s: (was: Remoting)
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