Give it a shot! I am glad things are easier on master. Let me find a
working example for you ...
From
https://github.com/geoserver/geoserver/wiki/Resource-API-Transition-Plan
GeoServerJ2eeRoleService GeoServer 2.5.x used:
File webXML = loader.find( "web.xml" );
Now it uses:
File webXML = GeoSe
Hi Jody
To summarize:
GeoServerResourceLoader resources =
GeoServerExtensions.bean(GeoServerResourceLoader.class );
resources.find("/accessDenied.jsp")
would do the job ?
Thanks
Christian
--
HPCC Systems Open Source Big
In older version of GeoServer GeoServerResource loader was insane and would
search in the servlet context as well! I moved this functionality to
GeoServerExtensions since it had a copy of the servlet context.
Still if you don't believe me here is it adding the location:
https://github.com/geoserv
Hi Jody
I think GeoServerResoureLoader does not help here. As far as I understand
the code the resource loader is for retrieving resources from the data
directory. I need
ServletContext.getRealPath(...)
to check if an optional access denied error page is reachable. (HTTP
response code 403).
At
You can use GeoServerResourceLoader to access webapp files in earlier
GeoServer versions. It is a bit magic hence the simplification and explicit
method.
jody
On Tuesday, June 10, 2014, Christian Mueller <
christian.muel...@os-solutions.at> wrote:
> Hi all
>
> Need some advice. I managed to fix
Hi all
Need some advice. I managed to fix this issue on master. Since this is a
bug I tried to backport to 2.5.x and 2.4.x. The patch uses
GeoserverExtensions.file(..)
to check if the accessDeniedPage exists.
But the file(...) method does not exist in 2.5.x and 2.4.x.
Should I backport the fil
There is already an issue
https://jira.codehaus.org/browse/GEOS-4943
The file does not exist but is used by the
GeoServerExceptionTranslationFilter.
The simplest solution is to kick out the accessDeniedErrorPage property. At
the moment, it is not possible to configure such a page using the admi
