You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Christiaan (JIRA)" <ji...@apache.org> on 2008/04/10 10:34:04 UTC
[jira] Created: (JCR-1529) Improve ease of installation for
deployment model 3: repository server
Improve ease of installation for deployment model 3: repository server
----------------------------------------------------------------------
Key: JCR-1529
URL: https://issues.apache.org/jira/browse/JCR-1529
Project: Jackrabbit
Issue Type: Improvement
Reporter: Christiaan
I think especially for people who are looking for the implementation of deployment model 3 (Model 3: The Repository Server) I would really like to see the following improvements for faster acceptance of JackRabbit:
On the server side:
1) A bundled installation for Tomcat and Jackrabbit so after installing the Jackrabbit repository is up and running (like the Slide project has);
2) For those who have already installed Tomcat a war file which also sets up the Jackrabbit repository with minimal configuration. If I understand it correcly I currently have to download about 15 individual jar files. Please bundle these as well!
For the client:
A small example how to acces the server repository from a (non-webapp) client. http://jackrabbit.apache.org/jcr-client-application-howto.html does not really describe this, unlike mentioned in http://jackrabbit.apache.org/repository-server-howto.html I personally think that this information is currently too much scattered over different pages, howtos, wikis, hops.
Also, http://jackrabbit.apache.org/repository-server-howto.html contains the following warning:
Warning: The current JCR-RMI library is designed for simplicity, not performance. You will probably experience major performance issues if you try running any non-trivial applications on top of JCR-RMI.
This does not promote acceptance either. How mature is this deployment model? Can it be used in production? What about the metioned alternative of WebDav protocol? Is this supported, how should it be configured? Slide uses the webdav protocol and has proven to be fine for production.
kind regards,
Christiaan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1529) Improve ease of installation for
deployment model 3: repository server
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1529.
--------------------------------
Resolution: Duplicate
Resolving as a duplicate of JCR-1357 where we implemented the jackrabbit-standalone server.
> Improve ease of installation for deployment model 3: repository server
> ----------------------------------------------------------------------
>
> Key: JCR-1529
> URL: https://issues.apache.org/jira/browse/JCR-1529
> Project: Jackrabbit
> Issue Type: Improvement
> Reporter: Christiaan
>
> I think especially for people who are looking for the implementation of deployment model 3 (Model 3: The Repository Server) I would really like to see the following improvements for faster acceptance of JackRabbit:
> On the server side:
> 1) A bundled installation for Tomcat and Jackrabbit so after installing the Jackrabbit repository is up and running (like the Slide project has);
> 2) For those who have already installed Tomcat a war file which also sets up the Jackrabbit repository with minimal configuration. If I understand it correcly I currently have to download about 15 individual jar files. Please bundle these as well!
> For the client:
> A small example how to acces the server repository from a (non-webapp) client. http://jackrabbit.apache.org/jcr-client-application-howto.html does not really describe this, unlike mentioned in http://jackrabbit.apache.org/repository-server-howto.html I personally think that this information is currently too much scattered over different pages, howtos, wikis, hops.
> Also, http://jackrabbit.apache.org/repository-server-howto.html contains the following warning:
> Warning: The current JCR-RMI library is designed for simplicity, not performance. You will probably experience major performance issues if you try running any non-trivial applications on top of JCR-RMI.
> This does not promote acceptance either. How mature is this deployment model? Can it be used in production? What about the metioned alternative of WebDav protocol? Is this supported, how should it be configured? Slide uses the webdav protocol and has proven to be fine for production.
> kind regards,
> Christiaan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.