You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/06/19 13:29:45 UTC
[jira] Created: (SLING-546) ObjectContentMnagerFactoryImpl does not
register adapter factories for mapped objects
ObjectContentMnagerFactoryImpl does not register adapter factories for mapped objects
-------------------------------------------------------------------------------------
Key: SLING-546
URL: https://issues.apache.org/jira/browse/SLING-546
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: 2.0.1
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: JCR OCM 2.0.2
After the change of the maven-sling-plugin to not set the immediate attribute anymore to true by default for components, the jcr/ocm ObjectContentManagerFactoryImpl class is registered as a delayed component. This causes the factory to only be instantiated when the the service is first requested and the bundle listener to only be registered by then.
Correct would be to immediately activate this component such that it can start listening for bundles and register adapter factories.
In addition, the service registration is incorrect as the component is registered as a service for all implemented interfaces. The reason for this is the incorrect attribute "name" to indicate the actual service interface. This should be the "interface" attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-546) ObjectContentMnagerFactoryImpl does not
register adapter factories for mapped objects
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-546.
-----------------------------------
Thanks for the feedback. I so close this issue.
> ObjectContentMnagerFactoryImpl does not register adapter factories for mapped objects
> -------------------------------------------------------------------------------------
>
> Key: SLING-546
> URL: https://issues.apache.org/jira/browse/SLING-546
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: 2.0.1
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR OCM 2.0.2
>
>
> After the change of the maven-sling-plugin to not set the immediate attribute anymore to true by default for components, the jcr/ocm ObjectContentManagerFactoryImpl class is registered as a delayed component. This causes the factory to only be instantiated when the the service is first requested and the bundle listener to only be registered by then.
> Correct would be to immediately activate this component such that it can start listening for bundles and register adapter factories.
> In addition, the service registration is incorrect as the component is registered as a service for all implemented interfaces. The reason for this is the incorrect attribute "name" to indicate the actual service interface. This should be the "interface" attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-546) ObjectContentMnagerFactoryImpl does
not register adapter factories for mapped objects
Posted by "Craig L. Ching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606415#action_12606415 ]
Craig L. Ching commented on SLING-546:
--------------------------------------
I've confirmed that my code and the simple-demo project in sling itself are working again. Thanks!
> ObjectContentMnagerFactoryImpl does not register adapter factories for mapped objects
> -------------------------------------------------------------------------------------
>
> Key: SLING-546
> URL: https://issues.apache.org/jira/browse/SLING-546
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: 2.0.1
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR OCM 2.0.2
>
>
> After the change of the maven-sling-plugin to not set the immediate attribute anymore to true by default for components, the jcr/ocm ObjectContentManagerFactoryImpl class is registered as a delayed component. This causes the factory to only be instantiated when the the service is first requested and the bundle listener to only be registered by then.
> Correct would be to immediately activate this component such that it can start listening for bundles and register adapter factories.
> In addition, the service registration is incorrect as the component is registered as a service for all implemented interfaces. The reason for this is the incorrect attribute "name" to indicate the actual service interface. This should be the "interface" attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-546) ObjectContentMnagerFactoryImpl does not
register adapter factories for mapped objects
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-546:
------------------------------------
Affects Version/s: (was: 2.0.1)
JCR OCM 2.0.2
> ObjectContentMnagerFactoryImpl does not register adapter factories for mapped objects
> -------------------------------------------------------------------------------------
>
> Key: SLING-546
> URL: https://issues.apache.org/jira/browse/SLING-546
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR OCM 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR OCM 2.0.2
>
>
> After the change of the maven-sling-plugin to not set the immediate attribute anymore to true by default for components, the jcr/ocm ObjectContentManagerFactoryImpl class is registered as a delayed component. This causes the factory to only be instantiated when the the service is first requested and the bundle listener to only be registered by then.
> Correct would be to immediately activate this component such that it can start listening for bundles and register adapter factories.
> In addition, the service registration is incorrect as the component is registered as a service for all implemented interfaces. The reason for this is the incorrect attribute "name" to indicate the actual service interface. This should be the "interface" attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-546) ObjectContentMnagerFactoryImpl does
not register adapter factories for mapped objects
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-546.
-------------------------------------
Resolution: Fixed
Implement fix in Rev. 669451.
Resolving now and will close this issue as soon as it is confirmed by Craig Ching, who reported it in [1].
[1] http://markmail.org/message/gv3zxtflogwgw54b
> ObjectContentMnagerFactoryImpl does not register adapter factories for mapped objects
> -------------------------------------------------------------------------------------
>
> Key: SLING-546
> URL: https://issues.apache.org/jira/browse/SLING-546
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: 2.0.1
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR OCM 2.0.2
>
>
> After the change of the maven-sling-plugin to not set the immediate attribute anymore to true by default for components, the jcr/ocm ObjectContentManagerFactoryImpl class is registered as a delayed component. This causes the factory to only be instantiated when the the service is first requested and the bundle listener to only be registered by then.
> Correct would be to immediately activate this component such that it can start listening for bundles and register adapter factories.
> In addition, the service registration is incorrect as the component is registered as a service for all implemented interfaces. The reason for this is the incorrect attribute "name" to indicate the actual service interface. This should be the "interface" attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.