This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 21324

Summary: Wrong implementation of JNDI provider should brake all JNDI related modules (JNDI, CORBA, Jezevec, RMI, EJB, Komodo,...)
Product: platform Reporter: Tomas Zezula <tzezula>
Component: -- Other --Assignee: Jaroslav Tulach <jtulach>
Status: CLOSED FIXED    
Severity: blocker    
Priority: P1    
Version: 3.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description Tomas Zezula 2002-03-07 19:05:10 UTC 
The org.netbeans.core.naming.Jndi sets itself as initialContextFactoryBuilder
which is WRONG!!!!
This object is singleton for the JDK VM instance, so all providers NIS, LDAP,
EJB, CosNaming, RMI, DNS, NDS, ... contexts are "transformed" into NetBeans
Context. The Jndi should NOT set the initialContextFactoryBuilder AT ALL.
This is needed only by browsers and similar tools, the right implementation of
InitialContextFactoryBuilder is part of JNDI module. See
org/netbeans/jndi/spi/NbInitialContextFactory.java and its registration in
org/netbeans/jndi/DirContext.java
Comment 1 Jaroslav Tulach 2002-03-08 15:27:36 UTC 
Excelent, can you tell me what to do? The only thing I can imagine is
to copy the jndi/spi/NbInitialCF into the core/naming/Jndi...

Is it acceptable solution?
Comment 3 Tomas Zezula 2002-03-08 18:21:34 UTC 
The patch works fine.
Thanks
Comment 4 Quality Engineering 2003-07-01 16:43:28 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.