You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/09/03 16:32:57 UTC
[jira] Created: (SLING-1097) ResourceResolverFactory service
missing after restarting repository
ResourceResolverFactory service missing after restarting repository
--------------------------------------------------------------------
Key: SLING-1097
URL: https://issues.apache.org/jira/browse/SLING-1097
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions: Engine 2.0.4
Reporter: Bertrand Delacretaz
Priority: Minor
Steps to reproduce:
1. Start launchpad/app
2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
The component is declared as follows in SlingMainServlet, looks ok to me:
/** @scr.reference cardinality="0..1" policy="dynamic" */
private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1097) ResourceResolverFactory service
missing after restarting repository
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751439#action_12751439 ]
Bertrand Delacretaz commented on SLING-1097:
--------------------------------------------
I briefly tested with the Felix SCR of revision 811360, but the repository doesn't start, without obvious error messages in the logs. One test fails in the build of that module anyway [1] so there might be other issues.
[1] test_SimpleComponent_configuration_ignore(org.apache.felix.scr.integration.ComponentConfigurationTest)
> ResourceResolverFactory service missing after restarting repository
> --------------------------------------------------------------------
>
> Key: SLING-1097
> URL: https://issues.apache.org/jira/browse/SLING-1097
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Steps to reproduce:
> 1. Start launchpad/app
> 2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
> 3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
> Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
> In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
> The component is declared as follows in SlingMainServlet, looks ok to me:
> /** @scr.reference cardinality="0..1" policy="dynamic" */
> private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1097) ResourceResolverFactory service
missing after restarting repository
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751441#action_12751441 ]
Felix Meschberger commented on SLING-1097:
------------------------------------------
You have to set the ds.factory.enabled system property. I will add this property to the Sling launcher in trunk soon.
The problem is, that the embedded repository bundle is depending on non-standard implementation we had in previous SCR implementations. In the current trunk state, I kept this behaviour for backwards compatibility but added a switch which must be set to enable this behaviour.
I am still unsure what really is correct: requiring the switch to be set to get the non-standard behaviour or requiring the switch to be set to disable non-standard behaviour. The standards part of me says "switch must enable", the user part of me says "switch may disable".
In short, just add
ds.factory.enabled=true
to the sling.properties and it should work.
> ResourceResolverFactory service missing after restarting repository
> --------------------------------------------------------------------
>
> Key: SLING-1097
> URL: https://issues.apache.org/jira/browse/SLING-1097
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Steps to reproduce:
> 1. Start launchpad/app
> 2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
> 3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
> Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
> In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
> The component is declared as follows in SlingMainServlet, looks ok to me:
> /** @scr.reference cardinality="0..1" policy="dynamic" */
> private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1097) ResourceResolverFactory service
missing after restarting repository
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1097.
--------------------------------------
Assignee: Felix Meschberger
Resolution: Fixed
I think we can mark this issue fixed, as it can be solved with the upgraded (long done) Apache Felix Declarative Services bundle.
> ResourceResolverFactory service missing after restarting repository
> --------------------------------------------------------------------
>
> Key: SLING-1097
> URL: https://issues.apache.org/jira/browse/SLING-1097
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Priority: Minor
>
> Steps to reproduce:
> 1. Start launchpad/app
> 2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
> 3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
> Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
> In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
> The component is declared as follows in SlingMainServlet, looks ok to me:
> /** @scr.reference cardinality="0..1" policy="dynamic" */
> private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1097) ResourceResolverFactory service missing
after restarting repository
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-1097.
------------------------------------
Done
> ResourceResolverFactory service missing after restarting repository
> --------------------------------------------------------------------
>
> Key: SLING-1097
> URL: https://issues.apache.org/jira/browse/SLING-1097
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Priority: Minor
>
> Steps to reproduce:
> 1. Start launchpad/app
> 2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
> 3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
> Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
> In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
> The component is declared as follows in SlingMainServlet, looks ok to me:
> /** @scr.reference cardinality="0..1" policy="dynamic" */
> private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1097) ResourceResolverFactory service
missing after restarting repository
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751319#action_12751319 ]
Felix Meschberger commented on SLING-1097:
------------------------------------------
This might be related to FELIX-1445. Upgrading to a trunk build of SCR might help.
(yes, a release is overdue)
> ResourceResolverFactory service missing after restarting repository
> --------------------------------------------------------------------
>
> Key: SLING-1097
> URL: https://issues.apache.org/jira/browse/SLING-1097
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Steps to reproduce:
> 1. Start launchpad/app
> 2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
> 3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
> Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
> In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
> The component is declared as follows in SlingMainServlet, looks ok to me:
> /** @scr.reference cardinality="0..1" policy="dynamic" */
> private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1097) ResourceResolverFactory service
missing after restarting repository
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751444#action_12751444 ]
Bertrand Delacretaz commented on SLING-1097:
--------------------------------------------
Indeed - setting ds.factory.enabled=true and updating to trunk SCR fixes the problem
> ResourceResolverFactory service missing after restarting repository
> --------------------------------------------------------------------
>
> Key: SLING-1097
> URL: https://issues.apache.org/jira/browse/SLING-1097
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.4
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Steps to reproduce:
> 1. Start launchpad/app
> 2. Stop and restart the org.apache.sling.jcr.jackrabbit.server bundle
> 3. http://localhost:8888/index.html now says "ResourceResolverFactory service missing, cannot service requests" which come from the SlingMainServlet's service() method.
> Stopping and restarting the org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl component has the same effect.
> In both cases, stopping and restarting the org.apache.sling.engine.impl.SlingMainServlet component solves the problem.
> The component is declared as follows in SlingMainServlet, looks ok to me:
> /** @scr.reference cardinality="0..1" policy="dynamic" */
> private JcrResourceResolverFactory resourceResolverFactory;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.