libreccm-legacy/ccm-ldn-search/doc/search-standalone
jensp b6492ca9be Diverser Kleinkram (unter anderem Abgleich ccm-bundle, einige Ergänzungen an Upgrades etc.)
git-svn-id: https://svn.libreccm.org/ccm/trunk@1646 8810af33-2d31-482b-a856-94f89814c4df
2012-05-08 08:46:31 +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 Next part of the conversion of CCM / APLAWS to be deployed in a standard way 2009-02-21 19:13:04 +00:00
bebop-show.tld Next part of the conversion of CCM / APLAWS to be deployed in a standard way 2009-02-21 19:13:04 +00:00
server-config.wsdd Next part of the conversion of CCM / APLAWS to be deployed in a standard way 2009-02-21 19:13:04 +00:00
web.xml Diverser Kleinkram (unter anderem Abgleich ccm-bundle, einige Ergänzungen an Upgrades etc.) 2012-05-08 08:46:31 +00:00

README

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

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

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