Hi Basit!
Did you provide a jndi.properties file ? Place it into a directory
where it could be found via the classpath. My personal favorite is the
working directory from where I issue the client start command. Also be
careful NOT to include a JAR file into the classpath that does contain
another jndi.properties. Otherwise the order of the entries in the
classpath will matter (which jndi.properties is found first ?) which I
consider as a bad thing. E.g. j2ee.jar from SUN does contain a
jndi.properties file. So do not include this one.
My jndi.properties looks like this:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=localhost
java.naming.factory.url.pkgs=org.jboss.naming
Did this help ?
Cheers,
Tobias
Basit wrote:
>
> hey
> i was trying ds = (DataSource) new InitialContext().lookup("java:/mySQL");
> conn = ds.getConnection(); in my entity bean code.
>
> when i run client , it prompts Provider URL missing ,
> javax.naming.ConfigurationException
>
> mysql is running smoothly ..
> my client code is as under
>
> ----
> InitialContext jndiContext = new InitialContext();
> System.out.println("Got context ..");
> Object ref = jndiContext.lookup("java:/mySQL");
> System.out.println("got reference");
>
> it prints Got context and but at Object ref = xxxx
> it throws NamingException - PRovider url missing
>
> any tip ?
>
> -=0 Basit
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
