On Sun, Feb 24, 2013 at 11:32 PM, sam <[email protected]> wrote: > ...So basically the flow I'm considering is this: > - External OBR comes online for product A-C > - Administrator examines OBR and contained bundles to verify content is > structured correctly as defined by the Sling-Initial-Content per bundle > - OBR is approved and is registered with central GW component > - OBR bundles are then installed (here though I'm not sure how to do this > atm, the bundles will go into Sling JCR and being accessible through Felix > is not really relevant) > - Content is now accessible by internal products A-C...
IIUC what you want to build is an OBR proxy, running on Sling, which hides artifacts that proxied OBRs provides, until those artifacts have been approved by an administrator. Is that correct? If yes, the above scenario looks good to me and is certainly feasible with Sling, but I don't see why you want OBR bundles to be installed in the Sling instance that runs the proxy. I don't think you need that, and it would mess up that Sling instance. The proxy just needs to consider those bundles as abstract artifacts that have requirements and capabilities. As you mention Karaf, note also http://blog.nanthrax.net/tag/obr/ - I don't know what the status of that is, but it might provide what you need, and looks like it uses a plugin-based storage architecture where you might be able to integrate a Sling repository. -Bertrand
