On 12/6/2012 4:39 AM, Heiko W.Rupp wrote:
> Hey Bill,
>
> Am 05.12.2012 um 22:37 schrieb Bill Burke:
>
>> Java EE 6 doesn't support EJB + JAX-RS components that are not deployed
>> under the WEB-INF/lib or WEB-INF/classes. SO, you must move
>> biz-stuff.jar into rest.war or create a JAX-RS servi
I think I found the solution.
When I put a class with @ApplicationPath inside the .war for /rest and omit it
from the .jar, the rest-api is available only on the /rest context
And in my case it still finds all classes with @Path inside the jar
Heiko
Am 06.12.2012 um 10:39 schrieb Heiko W.Rupp:
Hey Bill,
Am 05.12.2012 um 22:37 schrieb Bill Burke:
> Java EE 6 doesn't support EJB + JAX-RS components that are not deployed
> under the WEB-INF/lib or WEB-INF/classes. SO, you must move
> biz-stuff.jar into rest.war or create a JAX-RS service that delegates to
> the EJBs.
I don't exactly
Java EE 6 doesn't support EJB + JAX-RS components that are not deployed
under the WEB-INF/lib or WEB-INF/classes. SO, you must move
biz-stuff.jar into rest.war or create a JAX-RS service that delegates to
the EJBs.
But, Resteasy can support it your case with a special config switch.
r
Hi,
so I have in As7 the following situation:
rhq.ear/
coregui.war/ at /coregui
portal.war at /
rest.war/ at /rest
rest-examples.war/ at /rest-examples
biz-stuff.jar, containing the SLSBs implementing the REST-Interface
Now I want my rest-endpoints to live below
