[seam-issues] [JBoss JIRA] Commented: (SEAMSERVLET-3) @HttpParam
Dan Allen (JIRA)
jira-events at lists.jboss.org
Thu Apr 22 01:31:10 EDT 2010
[ https://jira.jboss.org/jira/browse/SEAMSERVLET-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12526925#action_12526925 ]
Dan Allen commented on SEAMSERVLET-3:
-------------------------------------
...and perhaps because it appears in these blog entries:
by Ken Gullaksen: http://www.glxn.net/?p=141
by Gavin: http://relation.to/Bloggers/InjectionPointMetadataAPIForWebBeans
I think we should consider using the annotations supported by JAX-RS. Clearly, we would be applying them in a different context, but it would allow the developer to use the same API (read: annotations) when information about the request needs to be injected. I'm expecting that the developer understands the different between a REST invocation and a delegate call from another bean. They are mutually exclusive.
@javax.ws.rs.CookieParam
@javax.ws.rs.HeaderParam
@javax.ws.rs.QueryParam
@javax.ws.rs.FormParam
@javax.ws.rs.MatrixParam (values in the URL delimited by a semi-colon, such as http://host.com/projects/catalog;name=Seam;lead=Pete Muir)
@javax.ws.rs.PathParam (not sure if this one really applies)
We should also consider supporting @DefaultValue like JAX-RS.
> @HttpParam
> ----------
>
> Key: SEAMSERVLET-3
> URL: https://jira.jboss.org/jira/browse/SEAMSERVLET-3
> Project: Seam Servlet
> Issue Type: Feature Request
> Reporter: Nicklas Karlsson
> Assignee: Nicklas Karlsson
>
> Implement the @HttpParam as outlined in the RefDoc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list