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 2650 - JNDI can`t run against rmiregistry
Summary: JNDI can`t run against rmiregistry
Status: CLOSED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: Karel Gardas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-07-22 16:31 UTC by Karel Gardas
Modified: 2003-07-02 16:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karel Gardas 1999-07-22 16:31:11 UTC 
java.lang.NoClassDefFoundError: com/sun/jndi/url/jndi/GenericURLContext
        at
        at com.sun.jndi.rmi.registry.RegistryContextFactory.getInitialContext(RegistryContextFactory.java:55)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:771)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:169)
        at javax.naming.InitialContext.<init>(InitialContext.java:146)
        at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:70)
        at com.netbeans.enterprise.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:44)
        at com.netbeans.enterprise.modules.jndi.JndiRootNode.addContext(JndiRootNode.java:209)
        at com.netbeans.enterprise.modules.jndi.JndiDataType$2.run(JndiDataType.java:89)
        at java.lang.Thread.run(Thread.java:479)



coose runtime / JNDI - create new context / factory:
com.sun.jndi.rmi.registry.RegistryContextFactory - type Context label and JNDI initial context (for example rmi://linux1:1099 and push OK button
Comment 1 Quality Engineering 2003-07-02 15:56:30 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verify.
Comment 2 Quality Engineering 2003-07-02 16:02:56 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.