You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/09/30 10:50:32 UTC
[jira] Created: (JCR-2335) Problems with jackrabbit-standalone
Problems with jackrabbit-standalone
-----------------------------------
Key: JCR-2335
URL: https://issues.apache.org/jira/browse/JCR-2335
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-standalone
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Fix For: 2.0.0
I'm having problems with the jackrabbit-standalone component not starting up properly because of two issues:
* The bundle packaging doesn't include the WEB-INF/config.xml file. I assume this is because of the more recent bundle plugin version treating whitespace differently in the inlining settings.
* The RMI binding fails if a local RMI registry is already running with another repository reference. I'm thinking of simply disabling the RMI registry bindings and using the http://localhost:8080/rmi address as the recommended RMI endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2335) Problems with jackrabbit-standalone
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2335.
--------------------------------
Resolution: Fixed
This is now fixed.
> Problems with jackrabbit-standalone
> -----------------------------------
>
> Key: JCR-2335
> URL: https://issues.apache.org/jira/browse/JCR-2335
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-standalone
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.0.0
>
>
> I'm having problems with the jackrabbit-standalone component not starting up properly because of two issues:
> * The bundle packaging doesn't include the WEB-INF/config.xml file. I assume this is because of the more recent bundle plugin version treating whitespace differently in the inlining settings.
> * The RMI binding fails if a local RMI registry is already running with another repository reference. I'm thinking of simply disabling the RMI registry bindings and using the http://localhost:8080/rmi address as the recommended RMI endpoint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.