Srinivas Naresh Bhimisetty wrote:
>
> Gili,
>
> jersey-test should run without any issues under Maven, when you invoke
> the package goal which creates the war file.
>
> May be you can refer the jmaki-backend jersey sample, which has some
> Provider classes. The test which runs on the Grizzly web container does
> run
> without any issue. BTW, which test container are you trying this with? Did
> you try that with the grizzly web test container?
Hi Naresh,
I am using the Grizzly web container. The JMaki sample you referred to isn't
the best example because it uses the package ResourceConfig. What I am
saying is that if you try using the ClasspathResourceConfig it will not find
the built-in Jersey providers. In fact, the JMaki example suffers from the
same problem. If you run it, you will notice it says:
INFO: Provider classes found:
class com.sun.jersey.samples.jmaki.config.JAXBContextResolver
Notice how none of the built-in providers show up.
Gili
--
View this message in context: http://jersey.576304.n2.nabble.com/Running-jersey-test-under-Maven-tp6191134p6198030.html
Sent from the Jersey mailing list archive at Nabble.com.