-
1. Re: Browsing jndi tree from Netbeans
juha Oct 1, 2002 6:33 PM (in response to aaime)check jndi.properties for the property values, and you will also need jnp-client.jar in your netbeans classpath (contains the org.jboss.naming.* classes referenced in the package properties)
-
2. Re: Browsing jndi tree from Netbeans
manik Oct 24, 2002 12:47 PM (in response to aaime)What version of Netbeans did you use?
I am having trouble (or rather, lack of knowledge) with connecting NetBeans 3.4 to jBoss 3.0.3.
I have jnp-client.jar in the NetBeans classpath, and NetBeans picks up the provider (org.jnp.interfaces.NamingContextFactory) just fine.
What do I use for an InitialContextFactory, and what are the default authentication details for jBoss (as I haven't changed any of the auth details in my installation)?
Finally, what would I use as a context root (java:/ ?) and a context label?
I have tried various entries for these fields, but I get an error stating: "Timeout value is too short to connect to service". Which I feel is irrelevant to whatever I typed in to the fields above. I have my JNDI timeout set to 10000 in the Netbeans options dialog.
Sorry for the long and somewhat spidery posting - I know I should have broken this up into several postings.
Help much appreciated... -
3. Re: Browsing jndi tree from Netbeans
juha Oct 24, 2002 6:40 PM (in response to aaime)By default all access to JBoss naming service is allowed, as far as I can remember, so authentication is most likely ignored even if you set it (unless you have secured the naming service yourself).
The root context is most likely "/" or just an empty string, "java:" will not be accessible from another JVM.
No clue what the context label thing is. -
4. Re: Browsing jndi tree from Netbeans
dubbeld Oct 25, 2002 8:35 AM (in response to aaime)Works for me with Netbeans 3.4. These are my settings.
Make sure that the following client jars are in classpath(in my case, I mounted archives in filesystems explorer):
jnp-client.jar
jboss-common-client.jar
log4j.jar
jnet.jar
Provider "NamingContextFactory" properties are:
JNDI Context Factory: org.jnp.interfaces.NamingContextFactory
JNDI Initial Context:
localhost:21099 (In my case since I run multiple instances of JBoss, if you did not change 1099)
Then I "connect using..."
And give my context a label which is used to show up in the explorer as a node.