"adrian(a)jboss.org" wrote :
| Now the class provides its own implementation of the Filter class.
| So we need to decide which of the two implementations is better
| (the provided one or the one I wrote).
|
| I'd say it would be easier in terms of maintenance to let FrameworkUtil
| provide new features of the filters rather than us having to keep up.
|
| That is unless there is a serious performance issue that needs to be addressed?
|
Although another issue is that we also want to be able filter other things besides
OSGi services. e.g. filtering on the INSTANCE scope properties of an MC bean.
Which almost certainly means letting the filter implementation bubble up into the MC
with an api that is OSGi agnostic and could contain extra features when not used
via the OSGi api.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251580#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...