Hi, On Mon, Sep 17, 2018 at 6:13 PM Jason E Bailey <[email protected]> wrote: > ...When I'm at a component level, I'm trying to identify what the original > content path/ resource is and there doesn't seem to be a way to do it...
Doesn't HttpServletRequest.getRequestPath help? Maybe the info is lost during component inclusion? If so the simplest way might be to save whatever information you need in request attributes in a filter that's active at the top of the component inclusion stack. -Bertrand
