Author: jharting Date: 2010-10-14 08:00:58 -0400 (Thu, 14 Oct 2010) New Revision: 13858 Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Webservices.xml Log: JBSEAM-4715 Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Webservices.xml =================================================================== --- branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Webservices.xml 2010-10-14 11:20:03 UTC (rev 13857) +++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Webservices.xml 2010-10-14 12:00:58 UTC (rev 13858) @@ -232,10 +232,17 @@ <para> First, get the RESTEasy libraries and the <literal>jaxrs-api.jar</literal>, deploy them with the other libraries of your application. Also deploy the integration library, - <literal>jboss-seam-resteasy.jar</literal>. + <literal>jboss-seam-resteasy.jar</literal>. </para> - <para> + In seam-gen based projects, this can be done by appending <literal>jaxrs-api.jar</literal>, <literal>resteasy-jaxrs.jar</literal> + and <literal>jboss-seam-resteasy.jar</literal> to the <literal>deployed-jars.list</literal> (war deployment) or + <literal>deployed-jars-ear.list</literal> (ear deployment) file. For a JBoss Tools based project, copy the libraries mentioned + above to the <literal>EarContent/lib</literal> (ear deployment) or <literal>WebContent/WEB-INF/lib</literal> (war deployment) + folder and reload the project in the IDE. + </para> + + <para> On startup, all classes annotated <literal&gt;(a)javax.ws.rs.Path&lt;/literal&gt; will be discovered automatically and registered as HTTP resources. Seam automatically accepts and serves HTTP requests with its built-in <literal>SeamResourceServlet</literal>. The URI of a resource is build as follows: @@ -512,6 +519,13 @@ <note> <para> + RESTEasy components do not support hot redeployment. As a result, the components should never + be placed in the <literal>src/hot</literal> folder. The <literal>src/main</literal> folder should + be used instead. + </para> + </note> + <note> + <para> Provider classes can currently not be Seam components. Although you can configure an <literal>@Provider</literal> annotated class as a Seam component, it will at runtime be managed by RESTEasy as a singleton with no Seam interception, bijection, etc. The instance will not be