Hi Arnaud,
please see inline...
On 03/21/2011 01:02 PM, Arnaud Bailly wrote:
> Hello Jakub,
> Here is an outline of those classes:
>
>
> package my.package.root;
>
> @Path("/data")
> public class RequestResources {
>
> @Context
> HttpConfiguration configuration;
>
> @GET
> @Path("/queries")
> @Produces(MediaType.APPLICATION_JSON)
> public String listAllQueries(@Rpc RequesterRpc rpc) {
> // do some stuff
> }
>
> @GET
> @Path("/outputs")
> @Produces(MediaType.APPLICATION_JSON)
> public String listAllOutputs(@Rpc RequesterRpc rpc) {
> // do some other stuff
> }
>
>
>
> What I really want to do is to customize the @Rpc injected interface in
> order to have different implementations between test and production.
Who is responsible for injecting the HttpConfiguration and the @Rpc
annotated parameters?
Could you share some more code? Anything related to the above class in
the log?
> and the dummy resources:
>
> @Path("/dummy")
> public class DummyResources {
>
> @GET
> public String run() {
> return "";
> }
> }
This is strange, as the above class should be sufficient for the Jersey
runtime to deploy the application.
Is it possible to extract a simple reproducible test case project?
Thanks,
~Jakub
>
>
> --
> View this message in context: http://jersey.576304.n2.nabble.com/Multiple-root-contexts-in-tests-tp6184016p6191973.html
> Sent from the Jersey mailing list archive at Nabble.com.
>