[
https://jira.jboss.org/jira/browse/JBSEAM-3889?page=com.atlassian.jira.pl...
]
Christian Bauer updated JBSEAM-3889:
------------------------------------
Component/s: WS
(was: Remoting)
Easier RestEasy paths
---------------------
Key: JBSEAM-3889
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3889
Project: Seam
Issue Type: Feature Request
Components: WS
Environment: JSF based apps
Reporter: John Ament
Assignee: Christian Bauer
The rest easy integration is missing a few important integrations that would make using
it in applications considerably easier.
- s:link integrated resource paths based on actions. If I have a restful service defines
as:
@Path("/viewimage")
@Name("viewImage")
public class ViewImage implements java.io.Serializable
....
@GET
@Path("/{username}/{filename}")
public byte[] viewImage(@PathParam("username")String
username,@PathParam("filename")String filename)
I should be able to define an s:link something like...
<s:link action="#{viewImage.viewImage}">
<f:param name="username" value="#{someBean.someValue}" />
<f:param name="filename" value="#{someBean.someOtherValue}" />
<h:outputText value="View Image" />
</s:link>
Or even a specialized graphicImage implementation that does soemthing similar...
<s:graphicImage action="#{viewImage.viewImage}">
<f:param name="username" value="#{someBean.someValue}" />
<f:param name="filename" value="#{someBean.someOtherValue}" />
</s:graphicImage>
Second, the resource path configuration in web.xml should be optional. The seam filter
should be able to pull out the resources without needing the resource servlet directly
handling the values.
--
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