Hi Sam
I am having trouble really understanding the use case. OBRs serve the
deployment of bundles, but I take it you are trying to centralize access
to services provided by various bundles? What do you mean by "local"
sling repository? An idenpendent JCR node in an independent OSGi
container? Since OBRs are basically bundle sources (much like a maven
repo), I am uncertain what you mean by gateway to an OBR. Could you
elaborate a bit more on you goals?
Regards,
Olaf
On 02/24/2013 11:08 AM, sam wrote:
I have been coming up to speed over the past week and some on the various
OSGi offerings and am specifically interested in what Sling has to offer for
an upcoming project.
Based on our requirements I have been toying with the idea of having a
centralized local instance(s) of Sling to act as a gateway to several remote
OBRs. This would permit administration and approval of what is visible to
connecting parties. I think moving forward in a PoC with an approach like
this it would be good to represent or possibly mirror the remote OBRs in a
local Sling *Repository per remote OBR configuration*.
Being fairly new to OSGi and the various offerings and ways of deployment I
am not certain if this is a sound idea or possibly if a better alternative
approach would be preferable? In addition, it is not clear to me how to best
set this up with Sling. I have read the documentation covering the
installation and upgrading of bundles but how to create a new and isolated
repository in Sling is not clear. The idea is that remote OBR foo.bar is
meant for product versions of foo.bar and all access to a local instance
should not inter-mix with anything outside of this. So really having a node
per product that represents a branch in one repository is not enough I
think.
For configuration, I'm looking at running Sling as a feature within Karaf.
Also here I'm not sure if this ideal but the separation provided by Karaf in
being able to easily add additional children is fairly attractive. Future
deployments of web applications into a new war feature is very possible, the
basic feature concept alone seems like it could be useful. I'm not sure if
this done often or if it is better to run Sling standalone?
Thanks
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/Feasible-Use-Case-tp4021906.html
Sent from the Sling - Users mailing list archive at Nabble.com.
