Improve the behaviour of OSGi in keeping with the OSGi way
----------------------------------------------------------
Key: ARIES-440
URL: https://issues.apache.org/jira/browse/ARIES-440
Project: Aries
Issue Type: Improvement
Components: JNDI
Affects Versions: 0.2
Reporter: Alasdair Nottingham
Assignee: Alasdair Nottingham
There are a few issuets with the way the JNDI core works. These are:
1. The core does the following:
i) Find an ICF service
ii) Get ICF
iii) Create a Context
iv) release ICF service
v) return Context
This means that the ICF cannot manage the lifecycle because it doesn't know
when the context is finished with. We should only release the service when the
context has been closed.
2. We do a lot of queries, which is kind of expensive. If we used a service
tracker we could remove all the queries and it would be more efficient and
perform some amount better.
3. Got some things wrong on ARIES-417. e.g.
i) The uber bundle didn't export the package for the URLObjectFactoryFinder
ii) The URLObjectFactoryFinder doesn't get the environment, so it can't do
things based on the JNDI environment, this is bad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
