Thanks Kiran....I suspected that I need to specify a separate jndi.properties 
file because if you notice the comment in the NamingService class it says, 

"Context.PROVIDER_URL in server jndi.properties."

So it says that the file present in /conf is a server side jndi.properties 
(whatever it means). And the error is certainly because of specifying the url 
in /conf/jndi.properties. This is evident by taking a look at 
org.jboss.naming.NamingService class code.

BTW, a few more interesting observations:

a) If I specify the url as "jnp://localhost:1099" in /conf/jndi.properties file 
then I receive a ClassCastException in JBoss while trying to instantiate 
NamingService.

b) I have my own properties file read/write mechanism built in my application. 
So I used my this properties file to specify these values and changed code to 
create InitialContext using these values from the properties file.

anyways, thanks. My application would still work though I'd love to find out 
the reasons for the warning.



View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942778#3942778

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942778


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to