>
> So the effect is that multiple physical directories must be searched for
> a given resource?
Correct.
The alias maps a given path to an external directory.
Ok, that's what i had understood.
Can you give an example of how you would like it to work?
Here is the description of the EDR (Extended Document Root) mecanism in
Websphere :
Let's assume i have the following application :
- Webapps/
- MyApplication/
- images/
- css/
- META-INF/
- WEB-INF/
- index.html
I can define an EDR directory in the configuration of my application so
that the ressource i access are first retrieved from my application and
then in the EDR directory if they don't exist in my application.
- /.../.../.../.../EDR/
- images/
- index.html
These directories are defined as "extension" of my application and another
important thing is that i can also extend files which are at the root of my
application (as index.html).
After a few more test with Tomcat i understand that :
- You cannot "extend" directory, if you define an external location which
math an existing directory of your application, the ressources of your
application become unreachable.
- As the documentation say "Using '/' as an aliasPath is not allowed.", you
cannot extend any ressource which is at the root of your application.
Things seems clear for me now, please tell if i have missed something.
Thank you in advance for your support.
On Wed, Nov 30, 2011 at 11:53 AM, Pid <[email protected]> wrote:
> On 29/11/2011 17:47, Sylvain Goulmy wrote:
> > Hi all,
> >
> > I'd like to know it is possible to have equivalent functionality to the
> > "extended document root" provided by the WebSphere product. This feature
> > allows you to define a location outside the webapp to make contribution
> > without having to redeploy the application. This mechanism first checks
> if
> > the resource is present in the application and if not will look for it in
> > the directory extension.
>
> So the effect is that multiple physical directories must be searched for
> a given resource?
>
>
> > I thought that the functionality provided by the new attribute aliases
> for
> > the configuration item <context> would have a similar behavior, but I see
> > another operation. First of all it is not possible to set an alias on the
> > context '/', making it necessary to declare all the directories in which
> > you want to make the contribution. Also when I set an alias for a
> directory
> > present in my webapp, it becomes a priority and files in my webapp are no
> > longer available.
> >
> > Do I understand correctly how this new attribute aliases has to be used ?
>
> The alias maps a given path to an external directory.
>
>
> > Is it possible with Tomcat 7 to set up a mechanism similar to the
> extended
> > document root of Websphere?
>
> Can you give an example of how you would like it to work?
>
>
> p
>
>
>
>
> --
>
> [key:62590808]
>
>
