[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-975) constraint by inclusion on remote calls object fields

Christophe Vigouroux (JIRA) jira-events at lists.jboss.org
Thu Jan 24 09:44:35 EST 2008


    [ http://jira.jboss.com/jira/browse/JBSEAM-975?page=comments#action_12396579 ] 
            
Christophe Vigouroux commented on JBSEAM-975:
---------------------------------------------

We just have the same need. We do not want to exclude certain fields, but we want to include juste those fields we need.

> constraint by inclusion on remote calls object fields
> -----------------------------------------------------
>
>                 Key: JBSEAM-975
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-975
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Remoting
>            Reporter: Zalder R
>         Assigned To: 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list