libreccm-legacy/ccm-atoz/doc/atoz-standalone
pb 63a9ed8e1c Abschließender Umbau des atoz Package. Upgrade Scripts enthalten.
git-svn-id: https://svn.libreccm.org/ccm/trunk@1623 8810af33-2d31-482b-a856-94f89814c4df
2012-04-30 21:38:47 +00:00
..
README Abschließender Umbau des atoz Package. Upgrade Scripts enthalten. 2012-04-30 21:38:47 +00:00
bebop-define.tld Weitere Umbauten AtoZ. 2012-04-14 23:22:50 +00:00
bebop-show.tld Weitere Umbauten AtoZ. 2012-04-14 23:22:50 +00:00
web.xml Abschließender Umbau des atoz Package. Upgrade Scripts enthalten. 2012-04-30 21:38:47 +00:00

README

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

Up to that version the package was named ccm-ldn-atoz and has then renamed to
ccm-atoz.

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