[
https://issues.apache.org/jira/browse/ARIES-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alasdair Nottingham resolved ARIES-417.
---------------------------------------
Resolution: Fixed
Fix Version/s: 0.3
> Add Generics to JNDI and allow more flexible mechanism to plug URL
> ObjectFactories in.
> --------------------------------------------------------------------------------------
>
> Key: ARIES-417
> URL: https://issues.apache.org/jira/browse/ARIES-417
> Project: Aries
> Issue Type: Improvement
> Components: JNDI
> Reporter: Alasdair Nottingham
> Assignee: Alasdair Nottingham
> Fix For: 0.3
>
>
> A couple of minor changes to JNDI (that touch most everything)
> 1. Make the JNDI code support generics in the API and implementation.
> 2. Common up the code for finding JNDI URL ObjectFactory implementations.
> 3. Allow an extra plug point for finding URL ObjectFactories. Some non-OSGi
> aware URL ObjectFactories may be provided in some environments and may
> therefore not be in the service registry. Although the best solution is to
> get them into the service registry that only works if you know all of them,
> as a result I'll add a plug point that allows some "smart" code to use some
> heuristics to find stuff.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
