libreccm-legacy/ccm-subsite/doc/subsite-standalone
pb d4dbe95668 Umbenennen ccm-ldn-subsite und erste Schritte Funktionserweiterung Konfiguration Subsite Eingangsseite.
git-svn-id: https://svn.libreccm.org/ccm/trunk@1328 8810af33-2d31-482b-a856-94f89814c4df
2011-12-09 22:32:36 +00:00
..
README Umbenennen ccm-ldn-subsite und erste Schritte Funktionserweiterung Konfiguration Subsite Eingangsseite. 2011-12-09 22:32:36 +00:00
bebop-define.tld Umbenennen ccm-ldn-subsite und erste Schritte Funktionserweiterung Konfiguration Subsite Eingangsseite. 2011-12-09 22:32:36 +00:00
bebop-show.tld Umbenennen ccm-ldn-subsite und erste Schritte Funktionserweiterung Konfiguration Subsite Eingangsseite. 2011-12-09 22:32:36 +00:00
web.xml Umbenennen ccm-ldn-subsite und erste Schritte Funktionserweiterung Konfiguration Subsite Eingangsseite. 2011-12-09 22:32:36 +00:00

README

Up to APLAWS version 1.0.4 subsite had been installed into its own
application context: [webapps]/ccm-ldn-subsite.

Now it is installed inside the main APLAWS application context along
with all other applications.

If shortcuts should be installed as its own web context again following
modifications are necessary:
1.  remove webapp="xxx" from application.xml
2.  move the files in this dir to WEB-INF/
3.  change src/com/ad/london/subsite/Subsite.java 
    method getServletContext() as back to "/files"
4.  edit __ccm__/.../xsl/index.xsl according the comment
5.  edit in ccm-ldn-aplaws /web/__ccm__/themes/aplaws/subsite.xml
    according to the comment
6.  Add the filter expression in web.xml-subsite.in into the
    main applications web.xml

Running it in its own webapplication context nevertheless is not suggestive.
It needs several xsl files of the main application (esp. core) for basic
operations, which hac been directly mapped from the main applications directory
tree into its own directory tree. So no module separation is possible, no
security context useable etc.