i think running scripts directly from the bundle without having to import it into the repository is a big advantage for complex projects. i hope this capability mechanism squales well when you have thousands of scripts in your system.
on questions concering scripts & java classes accessed from the scripts (e.g. HTL script accessing a sling model): - in the current scenario it's required to export all model classes via OSGi to be able to use them from the HTL script - is it possibe with this new approach to keep them private to the bundle, and still use them from the scripts included and served from this bundle? stefan >-----Original Message----- >From: Radu Cotescu [mailto:[email protected]] >Sent: Thursday, April 26, 2018 11:34 AM >To: Sling Dev >Cc: [email protected] >Subject: [proposal][osgi][scripting] redesigned scripts deployment and >resolution > >Hello Sling devs, > >Karl and I have been working for the past weeks on a new scripting >prototype that we've now pushed to the Whiteboard [1]. The module is an >add-on that allows developers to deploy scripts through bundles, with the >following core features: >standalone module that doesn't require any changes in Sling's current APIs >bundles that provide scripts are wired to this add-on and then the add-on >registers servlets on behalf of the scripting bundles (one servlet / >script) >resource types can now be versioned (they're expressed as OSGi >capabilities) >resource types can have explicit dependencies to other resource types, and >everything is controlled by the wiring provided by the OSGi framework >For the full details please check the documentation provided at [1]. We're >very interested in your opinions about this module, since we’d like to >integrate it into the next Sling Starter release. > >Thanks, >Radu and Karl > >[1] - https://github.com/apache/sling-whiteboard/tree/master/scripting- >resolver <https://github.com/apache/sling-whiteboard/tree/master/scripting- >resolver>
