[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] How (if possible at all) to control the way Jetty7 handles links in webapps folder.
|
Alex,
If you want that sort of control your best bet is to use the Context Deployment approach and use the xml file descriptors pointing to your webapps, the added benefit is this is how you get hot deployment with jetty as well
examples are in the contexts and contexts-available directories in the standard download
cheers,
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Wed, Oct 27, 2010 at 09:38, Alexei Mikhailov
<alexei.mikhailov@xxxxxxxxxxxx> wrote:
Hi all!
I'm trying out new Jetty7 (7.2.0, to be exact), and encountered a problem.
I usually keep web application war files somewhere in /usr/local/mystuff folder, and drop links into jetty's webapps folder.
Warfiles usually have some version identifier in name (like cookie-eater-1.3-postgres.war), whereas links in webapps don's (cookie-eater.war).
Now, when deploying application, Jetty 6 starts it with link's name (i.e. I can access it via my-server/cookie-eater), whereas Jetty 7 playing smart and uses original file/folder name (hence, started application will be accessible via my-server/cookie-eater-1.3-postgres).
This is rather annoying, since applications might be accessing each other, and have configuration files specifying names without version identifiers. Now I'll have to go and rename all the entries in files every time app's name changes. Nothing there that sed and awk can't do, but still...
So my question is whether this behavior (whether to use link's name or original file name as deployment path) can be controlled somehow? I haven't found any information on that so far.
Thanks in advance!
Alex-
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
