Problem with Resteasy integration and SeamResourceServlet

[hajdi]

Hi,

Currently Resteasy is integreted into Seam by means of SeamResourceServlet. Therefore JAX-RS resources are served under URL path that is configured for this servlet. This if problematic if one wants to serve RESTful services from other path than normal Seam resources (images, css etc).

Are there any plans to support serving JAX-RS resources under path different than specified for SeamResourceServlet or even with no path at all?

Besides SeamResourceServlet path, JAX-RS resource path is also additionally prefixed by resource-path-prefix (defaults to rest). Are there any plans to add configuration for disabling this prefix?

Current state of path configuration for JAX-RS resources is a showstopper IMHO because one have to serve them under "SeamResourceServlet path + resource-path-prefix" prefix and in the same time you cannot change SeamResourceServlet path to something different than "/seam/resource" because there are elements in Seam (like for example s:graphicImage tag) that have default path hardcoded and breaks when it is changed.

Regards,
Rafal Hajdacki

[hajdi]

Any info on this problem?

Regards,
Rafal

[hajdi]

Maybe somebody knows workaround for this problem?

[meetoblivion]

There's nothing stopping you from having multiple servlet paths for a single servlet.  I have mine defined like this:

   <servlet>
      <servlet-name>Seam Resource Servlet</servlet-name>
      <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>
   </servlet>
   <servlet-mapping>
      <servlet-name>Seam Resource Servlet</servlet-name>
      <url-pattern>/seam/resource/*</url-pattern>
   </servlet-mapping>
   <servlet-mapping>
      <servlet-name>Seam Resource Servlet</servlet-name>
      <url-pattern>/resources/*</url-pattern>
   </servlet-mapping>

[hajdi]

Thanks, this solves my first problem.
But still it seams impossible to get rid of resource-path-prefix.

[hajdi]

The other solution that I currently use is UrlRewriteFilter. With it you can set paths anyway you want. Nevertheless I think Seam should be more flexible when it comes to this configuration. And of course tags like s:graphicImage shouldn't have hard coded paths.