SOLVED!
Thanks to Martin for the support, this is his email that solved the
issue, hope this helps!
Martin wrote:
Ah, this may be the difference in servlet vs. filter behavior. If you
are not using root, there is no point in having the following element
in
the web.xml:
<init-param>
<param-name>com.sun.jersey.config.property.WebPageContentRegex</param-n
ame>
<param-value>.*\.css|.*\.png|.*\.jsp</param-value>
</init-param>
And I believe it will start working when you change the registration
from filter to servlet (it is needed to be configured as a filter if it
is put at root for the jsp templates to work, but once you don't have
it at root, it can be a servlet). I suspect that as long as it is a
filter, the prefix (/oAuth) is part of the resource path and that's why
your resources are not getting resolved (since you would have to change
the path templates to include the oAuth prefix). If you change the
registration to servlet (in case of using /oAuth/* prefix), it should
work.
I.e. in web.xml replace:
<filter> with<servlet>
<filter-name> with<servlet-name>
<filter-class> with<servlet-class>
<filter-mapping> with<servlet-mapping>
Regards,
Martin