libreccm-legacy/ccm-themedirector/doc/theme-standalone
pb 569eb2ab13 Weitere Bereinigung des Namensraums und heirloom themes (Verlegen der content type XSLs).
git-svn-id: https://svn.libreccm.org/ccm/trunk@1475 8810af33-2d31-482b-a856-94f89814c4df
2012-01-29 01:08:19 +00:00
..
README Weitere Bereinigung des Namensraums und heirloom themes (Verlegen der content type XSLs). 2012-01-29 01:08:19 +00:00
bebop-define.tld Umbenennen von ccm-ldn-theme in ccm-themedirector. 2011-03-27 11:27:05 +00:00
bebop-show.tld Umbenennen von ccm-ldn-theme in ccm-themedirector. 2011-03-27 11:27:05 +00:00
web.xml Weitere Bereinigung des Namensraums und heirloom themes (Verlegen der content type XSLs). 2012-01-29 01:08:19 +00:00

README

As of CCM version 6.6.1 package ccm-ldn-themes became a generic package and
has been renamed to ccm-themedirector.
All names below and anywhere in the files should be adopted accordingly.

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

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/theme/ThemeApplication.java 
    method getServletContext() as back to "/files"
4.  edit themes/.../xsl/index.xsl according the comment
5.  edit in ccm-ldn-aplaws /web/themes/static/aplaws/theme.xml
    according to the comment


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.