Hi, Am Donnerstag, den 03.04.2008, 12:00 +0200 schrieb Alexander Klimetschek: > Am 03.04.2008 um 10:06 schrieb Bertrand Delacretaz: > > > > My larger concern is that those resources, served by bundles, are not > > discoverable. What I love when working with a JCR repository (like on > > a unixish system) is that everything is very visible and hackable, in > > files and folders - and we lose this for those "magic" resources > > served by bundles. > > ACK. > > > We don't need to address this right now, but as David mentions in this > > thread there should be a way to "see" those bundle resources along > > with what's stored in the repository. > > _wish mode on_
JIRA is your friend here ;-) > > There was once the idea of a resource browser built into sling. > Haven't looked at Sling's trunk for a while - has it been done? I once had a prototype for testing ... but I think I lost it over deleting repositories --- this is the drawback of storing code in the repo ;-) > > _now christmas + easter together_ > > It could be a general place for displaying all kinds of magic > redirects, docroot mappings, servlet filters and whatever. Maybe also > a kind of simulator or debugger that shows the resolving for a given > URL. Sounds all very reasonable. Why don't you go create JIRAs for these ? I am sure, one day there will be fixes for some. Some things of course already exist: * magic redirects : There is a configuration page for this * docroot mappings: Same here * Servlet Filters: not visible direclty, but in the configuration status you filter services * ... Agreed that this all requires some intimate knowledge and some kind of consolidation would certainly make sense. For example, Servlet Filters are expected to be reflected in the Resource Tree - which would allow scripted filters - as per SLING-199 such that they may be visible in the resource tree browser. Regards Felix
