Bertrand Delacretaz wrote:
Hi,
Working on SLING-351 I noticed that /sling/sling.js is not accessible,
as the OSGi console is mounted on /sling.
I suggest moving that path to /bundles/sling/sling.js, where /bundles
makes it clear that this resource comes from a bundle.
WDYT?
Hmm, I'm not sure :) - I think it shouldn't be of interest for the
client to know where the js comes from (bundle vs repository).
But I don't have any good suggestion for a better path yet.
Furthermore I think we should move the js to a different bundle. The
post servlets are of general use (with or without the script). I could
imagine that over time, the js lib might evolve while the post servlets
do not. With shipping the js together with the post servlets we create a
contract we can't break later on.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
