| Re: [jetty-users] My CORS proxy using Jersey (for JAX-RS) with Jetty 9.4.31 doesn't respond |
I've just noticed something in the error message:
| URI: | /feed/webresources/corsproxy/raw |
|---|---|
| STATUS: | 404 |
| MESSAGE: | Not Found |
| SERVLET: | default |
Powered by Jetty:// 9.4.31.v20200723
Actually, "default" is the name of the default servlet, the first mentioned in web.xml but the kind of URL should be handled by the second servlet mentioned in web.xml that uses Jersey whose name is "fr.gouesse.julien.jaxrs.RedFeedAggregatorApplication". Should I move the CORS proxy into another WAR and use another deployment context?
> Message du 06/08/20 22:47
> De : "Simone Bordet" <sbordet@xxxxxxxxxxx>
> A : gouessej@xxxxxxxxx
> Copie à : "Simone Bordet" <sbordet@xxxxxxxxxxx>, "JETTY user mailing list" <jetty-users@xxxxxxxxxxx>
> Objet : Re: [jetty-users] My CORS proxy using Jersey (for JAX-RS) with Jetty 9.4.31 doesn't respond
>
> Hi,
>
> On Thu, Aug 6, 2020 at 8:15 PM <gouessej@xxxxxxxxx> wrote:
> > 2020-08-06 20:09:07.840:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@1d31475{/feed,file:///opt/jetty/temp/jetty-0_0_0_0-8080-red-feed-aggregator_war-_feed-80_13_94_99-1302284637019804290.dir/webapp/,AVAILABLE,80.13.94.99}{/opt/web/mybase/webapps/red-feed-aggregator.war}
>
> So your application is deployed on contextPath /feed.
>
> This means @ApplicationPath("feed"), @Path("/webresources/corsproxy"), etc.
>
> --
> Simone Bordet
> ----
> http://cometd.org
> http://webtide.com
> Developer advice, training, services and support
> from the Jetty & CometD experts.
>