RFR: 8223260: NamingManager should cache InitialContextFactory

Seán Coffey sean.coffey at oracle.com
Thu Feb 6 17:54:48 UTC 2020

the current proposal is still:

I'd like to make the specification change in a follow on bug ID (if that 
works for people)


On 06/02/20 17:49, Alan Bateman wrote:
> On 06/02/2020 15:32, Seán Coffey wrote:
>> InitialContextFactory itself is an extremely simple interface with 
>> one method. I've browsed some code bases and could only find a small 
>> number of such Factories implementations with simple logic to return 
>> a Context. Applications will most likely delegate to the same Factory 
>> over and over also (albeit, it's all controlled by HashTable 
>> parameters). The new caching logic should help memory pressure here 
>> and not hinder it. I'm not seeing a major concern with current 
>> solution as a result.
> Okay, although I could imagine a non-JDK InitialContextFactory 
> implementation keeping a graph of objects alive. I saw your mail about 
> separating the clarification in the APIs docs so does it mean the 
> proposal on the table is the last webrev or is there a new version?
> -Alan

More information about the core-libs-dev mailing list