Re: [exoplatform] exo-jcr deployment models

[Gennady Azarenkov <gazarenkov@xxxxxxxxx>]

hi Alex,

> My first question is regarding the possible deployment models
> supported by exo-jcr. Jackrabbit is discribing its possible deployment
> models here: http://incubator.apache.org/jackrabbit/arch/deploy.html.
> More or less these can be summarized as:
> 1/ application bundled repository (a single application is able to
> access the repository)
> 2/ JVM bundled repository (multiple applications in the same JVM may
> access the repository;
> repository factory should be retrieved using JNDI lookups)
> 3/ separate JVM repository: multiple applications may access the
> repository through different
> protocols (f.e. RMI).
> However, it is written in jackrabbit documentation that the scenario
> 3/ (access through RMI) is not
> able yet to provide performance :-).
> Now my questions:

> 1/ where can I find more documents about the exo-jcr implementation?
for sure the most useful documentation for JCR still the JSR-170 
specification :-)
as exo-jcr conforms it, well there are some implementation specific stuffs -
like configuration, nodetype registry, security model etc. for a while we do 
not
have any well formed guide about (we are working on that of course) so
you can try to find some info in the project's forum, mail list and wiki 
docs
and of course ask your questions there.

> 2/ exo-jcr is working as in the above scenarios?
> 3/ Is scenario 3 possible? What are the pros and cons of scenario 3?
i would say yes (do not forget about WebDav :) btw), we have not
tried RMI yet but i do not see any fundamental problem, it is the matter of 
time

BR,

Gennady Azarenkov
eXo platform