Hi and thanks for the response. This looks to be pretty much what I'm looking for: http://sling.apache.org/site/content-loading-jcrcontentloader.html <http://sling.apache.org/site/content-loading-jcrcontentloader.html>
I want to structure an existing bundle in such a way that it can be loaded in the Sling JCR in an unstructured way. These Bundles are located in remote OBRs. You can register remote OBRs with Felix making those bundles accessible. This Felix instance will be administered and will be the central GW for obtaining info from the remotes. An administrator will explicitly add or remove these OBRs based on business criteria but all internal consumers can only access this information through the GW and that information is presented in an unstructured format through Sling's REST based APIs 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 So by making all content structured and layed out correctly through use of the Sling-Initial-Content header then a provider and consumer may agree upon a contract. I'm looking at this approach because often the consumers internally will not be able to leverage the bundles directly since many are non-OSGi based. My hope is that this way a decent generic distribution channel can be defined. This is still very early but I'm liking what I see so far. It is also good to see that these technologies are leveraged in commercial based products such as some of the blogs I have read on Adobe. So there has already been some trial by fire so to speak :) -- View this message in context: http://apache-sling.73963.n3.nabble.com/Feasible-Use-Case-tp4021906p4021933.html Sent from the Sling - Users mailing list archive at Nabble.com.
