[
https://issues.apache.org/jira/browse/FELIX-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310549#comment-14310549
]
David Jencks commented on FELIX-4785:
-------------------------------------
cf my original attempt to discuss this april 16-may 14 2014:
http://felix.markmail.org/message/ysjwfztinovvo7k5?q=from:david_jencks%40yahoo%2Ecom+list:org%2Eapache%2Efelix%2Edev&page=3
http://felix.markmail.org/message/h7seohu2polq6aza?q=from:david_jencks%40yahoo%2Ecom+list:org%2Eapache%2Efelix%2Edev&page=2
http://felix.markmail.org/message/6iux52gysnjg7fnv?q=from:david_jencks%40yahoo%2Ecom+list:org%2Eapache%2Efelix%2Edev&page=2
I have a hard time equating this with giving users no warning.
I will have to study your proposal in more detail.
IIRC the actual implementation objects were exposed through the old API. If we
keep it I would really prefer to copy the info into more DTO like objects.
The operations in the old API are just wrong and need to be disabled. They act
on the wrong logical layer of objects. They cannot be made to work in a
sensible way.
The old API was flawed in that it conflated the two levels of DTO, Basing the
old info on the current objects will return different information than it used
to and in particular for components that have no ComponentConfigurationDTO will
return nothing at all. It seemed impractical and pointless to me to expose the
same info through the old interfaces as used to be exposed, but if you want to
try to make it work I will not try to remove it, although I think a fragment
bundle might be a more appropriate location. I will seriously consider forking
the project for my own use rather than go back to the incorrect data model
being forced into the actual runtime classes.
The only tool I'm aware of that used the old data model was the web console,
which (although I haven't actually tried it) ought to show the correct
information now through the SCRInfo service which now uses the new data model.
Are there actually any other tools using the old data model?
> 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)
