[forge-issues] [JBoss JIRA] (FORGE-838) RestPlugin should support the right semantics for entities with non auto-generated Ids
George Gastaldi (JIRA)
jira-events at lists.jboss.org
Sat Oct 12 00:58:26 EDT 2013
[ https://issues.jboss.org/browse/FORGE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Gastaldi updated FORGE-838:
----------------------------------
Fix Version/s: 2.x Future
(was: 1.x Future)
> RestPlugin should support the right semantics for entities with non auto-generated Ids
> --------------------------------------------------------------------------------------
>
> Key: FORGE-838
> URL: https://issues.jboss.org/browse/FORGE-838
> Project: Forge
> Issue Type: Feature Request
> Components: Java EE APIs
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> Currently, the generated REST resources contain a {{@POST}} method for creating new entities and a {{@PUT}} method for updating an existing entity.
> This set of semantics is appropriate for auto-generated Ids where the Ids would be created by the server, and cannot be specified by the client.
> However, for JPA entities that do not contain a {{@GeneratedValue}} annotation, these semantics may not be unsuitable. It would be preferable to use only a {{@PUT}} method that is used to create and update the entities. This is primarily because the client gets to decide the resource/entity identifier, and hence, also the location of the resource.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the forge-issues
mailing list