Hi, Am Montag, den 19.11.2007, 10:47 +0100 schrieb Juanjo Vázquez: > Accordingly, I´m wondering if Sling is intended to > support all the next situations: > > 1 Sling distribution = 1 application + 1 JCR Repository
This is probably the default, right ? So I assume this must be supported. > 1 Sling distribution = n applications + 1 JCR Repository > 1 Sling distribution = n applications + n JCR Repositories I am not sure, what you mean by "application". I understand a "Sling Application" to be a bunch of OSGi bundles deployed to a single Sling instance. So if the bundles are well behaved (whatever that means, but it sounds cool) and for example respect each other's repository space there should be no problem of installing multiple "Sling Applications" in the same Sling instance. Now, for these applications using multiple repositories: This is more daunting as a single Sling instance is generally set up with a specific workspace (the default workspace) which the SlingAuthenticator logs in to. If a certain Sling Application uses another repository, it has to setup the connection and authentication itself (yes, the respective repository bundles may be of help here, of course). This raises the question: Running multiple Sling instances in the same VM: This is quite possible by for example having a servlet container and deploying multiple Sling instances as multiple web applications. Each Sling instance can be configured to use a separate repository (or each may use the same). > For instance, I´m not sure if Sling or microsling should enable to get a RMI > deployed repository. Yes, for Sling the jcr/jackrabbit-client project allows accessing a non-embedded repositories using JNDI or RMI. microsling only allows accessing a repository available in the same VM in the default Jackrabbit way. Regards Felix
