No, that jndi.properties file is needed to enable the use of the no arg InitialContext ctor. If you pass the Context.PROVIDER_URL property to the env used to create an InitialContext in your app this is the same as including a jndi.properties file with the provider url and both go through the RMI transport layer to communicate with JNDI. When this is done in the server is when you get problems with ClassCastExceptions on redeployment due to issues with how RMI Class.forName uses cache the old classes.
Really the problem in both cases is the specification of the provider url as this is what triggers the RMI transport. Simply remove that when doing lookups inside of the JBoss server and this problem goes away. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Camus Chan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 6:51 PM Subject: RE: [JBoss-user] Re: redeployment and classloading > Hi, > > I am using JBoss 3.0.3 and I have similar problem for a long while when > using JDK1.4.x (but no such problem in JDK1.3). > > Regarding the jndi-file, do you mean the jndi.properties ? I can only find > that file in server/default/conf/jndi.properties but not in all of my > deployed jar files. > > So, should I just remove the jndi.properties file from the conf directory > will make it works ? Thanks for your follow up. > > Camus ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
