On Thu, Apr 26, 2018 at 2:53 PM, Bertrand Delacretaz <[email protected]> wrote: > Hi Radu, > > On Thu, Apr 26, 2018 at 11:34 AM, Radu Cotescu <[email protected]> wrote: >> ...The module is an add-on that allows developers to deploy scripts through >> bundles... > > Thanks for this, interesting! > > IIUC it is then possible for a script coming from the repository and > another one coming from your module to be "mounted" to the same > resource type, HTTP method etc.
Yes, just like today it can come already from the repository and a servlet. > Is there a deterministic choice of which scripts "wins" in such a > case? Maybe that concern is outside of your module and belongs to the > general script/servlets resolving mechanism - I forgot how that's > handled there. Thats the nice part about it. This is a pure add-on that uses only the normal sling resource type handling. As such, it is fully compatible with what is available today. In your case, as you already guessed, that is purely part of how sling handles the case of two providers for the same resource type. > Also (and as usual ;-) I am a bit skeptical about the module's name - > I think we already have a scripts resolver, and your new module is > more specific than that. How about naming it "bundled scripts > extension", "script bundler" or something like that that's more > specific? Yeah, the name could be improved (I'm well-known for being terrible at naming things :-) regards, Karl > -Bertrand -- Karl Pauls [email protected]
