You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Adam Pilkington (JIRA)" <ji...@apache.org> on 2014/09/11 10:48:33 UTC
[jira] [Created] (ARIES-1244) Allow external access to Felix<->OSGi
adapters in org.apache.aries.subsystem.obr.internal
Adam Pilkington created ARIES-1244:
--------------------------------------
Summary: Allow external access to Felix<->OSGi adapters in org.apache.aries.subsystem.obr.internal
Key: ARIES-1244
URL: https://issues.apache.org/jira/browse/ARIES-1244
Project: Aries
Issue Type: Wish
Components: Subsystem
Reporter: Adam Pilkington
Priority: Trivial
Hi, I'm currently writing code that accesses Felix repositories and then allows interaction with these repositories via OSGi interfaces. This is something that Aries does inside the org.apache.aries.subsystem.obr.internal package where there are a number of classes which provide the ability to adapt OSGi->Felix and Felix->OSGi. The classes in question are
FelixCapabilityAdapter.java
FelixProperty.java
FelixRepositoryAdapter.java
FelixRequirementAdapter.java
FelixResourceAdapter.java
OsgiCapabilityAdapter.java
OsgiContentCapability.java
OsgiIdentityCapability.java
OsgiRequirementAdapter.java
OsgiResourceAdapter.java
Rather than re-invent the wheel/take a copy, I would like to propose that these classes are moved into their own package, and that this is subsequently exported for external use. Scanning the import statements, none of them look to reference any Aries internal classes and so I believe a simple refactoring is all that would be required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)