[opencms-dev] why the long servlet path, how to change

[Martin Leja]

Wouldn't it be reasonable to collect such detailed explanations as yours in
some kind of knowledge base or at least in a FAQ section?

----- Original Message -----
From: "Michael Emmerich" <Michael.Emmerich at framfab.de>
To: <opencms-dev at www.opencms.org>
Sent: Tuesday, October 29, 2002 4:30 PM
Subject: AW: [opencms-dev] why the long servlet path, how to change


> Martin, Bart,
>
> this is correct if you want to change the servlet path in OpenCms, you
have
> to do two things:
>
> 1) Modifiy the servlet-mapping in the web.xml as Bart did.
> 2) Adapt the path in the opencms.properties "url_prefix_http" to the new
> servlet path.
>
> Why is this second change required?
> OpenCms is able to generate static exports of the website created by the
> system. Since it it possible to export only a part of the site to the
> webserver, the links between the exported and not-exported parts of the
> pages must be modified during the export process. This mechanism is also
> used for the preview function of the OpenCms workpalce (which did not work
> after Bart's changes).
>
> The "url_prefix" parameters defines, where the OpenCms can find either the
> dynamically genrated pages (url_prefix_http), the static exported ones
> (url_prefix_export) or those useing https (url_prefix_https).
>
> Please note: If you modify the servlet path from
> "/[applicationname]/[servlet]/" to "/[applicationname]/", you cannot use
the
> static export with its default location (which is inside the
webapplication
> directory), as all requests in this webapplication are now forwared to the
> OpenCms servlet.
>
> Regards,
> Michael Emmerich
>
> OpenCms Professional Services
> Framfab Deutschland

[...]