You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/03/24 10:35:27 UTC

[jira] Created: (SLING-1460) Move SlingSettingsService to API bundle

Move SlingSettingsService to API bundle
---------------------------------------

                 Key: SLING-1460
                 URL: https://issues.apache.org/jira/browse/SLING-1460
             Project: Sling
          Issue Type: Improvement
          Components: API, Engine
    Affects Versions: API 2.0.8, Engine 2.0.6
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Engine 2.1.0, API 2.0.10


As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:

- Add the interface to the API in the o.a.s.api.services package
- Deprecate the interface in the enigne bundle and let it extend
  from the interface in the API
- Let the service impl in the engine bundle register itself for
  both interfaces.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SLING-1460) Move SlingSettingsService to new Settings bundle

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-1460:
------------------------------------

              Summary: Move SlingSettingsService to new Settings bundle  (was: Move SlingSettingsService to API bundle)
        Fix Version/s: Settings 0.1.0
                           (was: API 2.1.0)
    Affects Version/s:     (was: API 2.0.8)
          Component/s: Extensions
                           (was: API)

> Move SlingSettingsService to new Settings bundle
> ------------------------------------------------
>
>                 Key: SLING-1460
>                 URL: https://issues.apache.org/jira/browse/SLING-1460
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine, Extensions
>    Affects Versions: Engine 2.0.6
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Engine 2.1.0, Settings 0.1.0
>
>
> As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:
> - Add the interface to the API in the o.a.s.api.services package
> - Deprecate the interface in the enigne bundle and let it extend
>   from the interface in the API
> - Let the service impl in the engine bundle register itself for
>   both interfaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (SLING-1460) Move SlingSettingsService to new Settings bundle

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-1460.
------------------------------------


Close after release

> Move SlingSettingsService to new Settings bundle
> ------------------------------------------------
>
>                 Key: SLING-1460
>                 URL: https://issues.apache.org/jira/browse/SLING-1460
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine, Extensions
>    Affects Versions: Engine 2.0.6
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Settings 1.0.0, Engine 2.1.0
>
>
> As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:
> - Add the interface to the API in the o.a.s.api.services package
> - Deprecate the interface in the enigne bundle and let it extend
>   from the interface in the API
> - Let the service impl in the engine bundle register itself for
>   both interfaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SLING-1460) Move SlingSettingsService to new Settings bundle

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1460.
-------------------------------------

    Resolution: Fixed

Created new module and moved the service to this module. Updated all references.
The new implementation reads a possibly available sling id from the engine bundle on startup for compatibility

> Move SlingSettingsService to new Settings bundle
> ------------------------------------------------
>
>                 Key: SLING-1460
>                 URL: https://issues.apache.org/jira/browse/SLING-1460
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine, Extensions
>    Affects Versions: Engine 2.0.6
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Engine 2.1.0, Extensions Settings 0.1.0
>
>
> As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:
> - Add the interface to the API in the o.a.s.api.services package
> - Deprecate the interface in the enigne bundle and let it extend
>   from the interface in the API
> - Let the service impl in the engine bundle register itself for
>   both interfaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (SLING-1460) Move SlingSettingsService to API bundle

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reopened SLING-1460:
-------------------------------------


As mentioned in the mailing list, reopening this issue.

This service should not be part of the Sling API but a new module with the settings service.
The run mode stuff will be merged into this bundle as well.

> Move SlingSettingsService to API bundle
> ---------------------------------------
>
>                 Key: SLING-1460
>                 URL: https://issues.apache.org/jira/browse/SLING-1460
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine, Extensions
>    Affects Versions: Engine 2.0.6
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Engine 2.1.0, Settings 0.1.0
>
>
> As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:
> - Add the interface to the API in the o.a.s.api.services package
> - Deprecate the interface in the enigne bundle and let it extend
>   from the interface in the API
> - Let the service impl in the engine bundle register itself for
>   both interfaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SLING-1460) Move SlingSettingsService to API bundle

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1460.
-------------------------------------

    Resolution: Fixed

Changed in revision 927001

> Move SlingSettingsService to API bundle
> ---------------------------------------
>
>                 Key: SLING-1460
>                 URL: https://issues.apache.org/jira/browse/SLING-1460
>             Project: Sling
>          Issue Type: Improvement
>          Components: API, Engine
>    Affects Versions: Engine 2.0.6, API 2.0.8
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Engine 2.1.0, API 2.1.0
>
>
> As discussed in the mailinglist, the SlingSettings service should be moved to the API bundle:
> - Add the interface to the API in the o.a.s.api.services package
> - Deprecate the interface in the enigne bundle and let it extend
>   from the interface in the API
> - Let the service impl in the engine bundle register itself for
>   both interfaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.