Hi, Mike Müller schrieb: > Hi > > I'm reviewing the documentation on the Sling Site and need your help > do determine old stuff, because I'm not sure if they are up-to-date or not. > > So please give me some feedback on the following pages: > > - Architecture (seems to be up-to-date) [1]
Yes, this is up to date, since it has only recently been written by me. > - Eventing and Jobs (can someone check) [2] > - Internationalization Support (can someone check, seems to be outdated, > at least there's no getLocale() on SlingHttpServletRequest) [3] > - Installing and Upgrading Bundles (can someone check seems to be outdated > in favour of Felix management console) [4] While the contents is still correct (except for the reference to Sling Web Console instead of the Felix Web Console), this page should probably be dropped. Maybe we should just create a general page on system managament and refer to various options like the Felix Web Console or the Felix Shell (soon there will be a standardized Shell) > - Assembly (can someone check, seems not to be part of Sling, maybe CRX) [5] It was part of Sling and is now in the whiteboard. This mechanism predates our knowledge about the OSGi Deployment Admin Service and was an attempt to mimick Eclipse Features. I agree with Bertrand, that we should drop this page. > - Apache Sling Rewriter (maybe ok, but can't find > org.apache.sling.rewriter.*) [6] > - Groovy Support (seems to be ok) [7] We might want to drop this page. Since Groovy 1.6 the groovy library is a bundle and can directly be deployed into any OSGi Container and is also supported by Sling. We even included it in the standard Sling 5 binary. > - XSLT Processing Pipeline (seems to be ok) [8] > - Maven Sling Plugin (can someone check) [9] This page might be incomplete because the latest version of the plugin supports uploading bundles into the repository to support the JCR Install functionality. HTH Regards Felix
