[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4186) HTTP caching for SeamResourceServlet resources

[ https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl... ] Ashish Tonse updated JBSEAM-4186: --------------------------------- Attachment: restful-remoting.diff Attached patch changes the s:remote definition to a URI format that the browser can cache: This allows for /remoting/arbitrary-string/interface.js to be handled by the handler for /interface.js and shouldn't break the handlers for /subscription and /poll Old: /seam/remote/interface.js?componentName1,componentName2 New: /seam/remote/componentName1;componentName2/interface.js InterfaceGenerator checks to see that the path is valid and extracts component names from the path. I haven't done any HTTP caching stuff. Also, in the s:remote renderer, I am rendering a urlencoded %3B instead of ";" because tomcat requires the semicolons to be urlencoded to properly handle them. (Ref: https://issues.apache.org/bugzilla/show_bug.cgi?id=30535#c3) -- 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