[
https://issues.apache.org/jira/browse/FELIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323748#comment-14323748
]
Carsten Ziegeler commented on FELIX-4785:
-----------------------------------------
Thanks David, so what about these:
- I think o.a.f.scr.info might be a good package for ScrInfo.
- Component#getComponentInstance returning null: ok, I guess that's the best
option we have
- ScrInfo#config: right, if we have a new service in a new package, we can
easily hook it up. Maybe we can also simply delegate all methods to the new
service?
- I see your point with enableComponent/disableComponent : let's make it a noop
> Incompatible SCR API
> --------------------
>
> Key: FELIX-4785
> URL: https://issues.apache.org/jira/browse/FELIX-4785
> Project: Felix
> Issue Type: Bug
> Affects Versions: scr-2.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: scr-2.0.0
>
>
> Current trunk contains version 2.0.0 of the org.apache.felix.scr API package.
> While this is a logical step, this makes the new implementation unusable as a
> drop-in replacement into existing installations which might use the 1.x
> version of that API.
> I think we should go a more moderate way, leave the 1.x version in but
> deprecate it and also provide the replacement API (if any). Then in one of
> the further versions along the road, we can remove the API. This gives our
> users a chance to migrate slowly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
