Closed asafbennatan closed 1 year ago
PR contributed
@asafbennatan thanks for the finding! I guess this should be fixed in resteasy-core
, I'll submit issue to it.
@liweinan once created could you link to this issue - so i can follow its progress ? - Thanks
@asafbennatan sure
PR submitted in the upstream project: https://github.com/resteasy/resteasy/pull/3379
digging further i think i found the issue:
notice this line specifically:
servletRegistrationBean.addInitParameter(Application.class.getTypeName(), applicationClassName);
now look at the ServletContainerDispatcher code from resteasy core
specifically
String application = bootstrap.getInitParameter("jakarta.ws.rs.Application");
whileApplication.class
resolves tojakarta.ws.rs.core.Application
causing application to allways be nullthis matters because later in the ServletContainerDispatcher code we check if application is not null ,in this case we call process application which in turn calls
getClasses
andgetSingletons
not sure if the fix should be in this repo or in the resteasy core repo