classpath issues and system properties
Hi, I am using tomcat 4.1.24. I have a couple of questions. 1. Online documentation about class loader says, System class loader operates on CLASSPATH. I have included j2ee.jar in my CLASSPATH, but tomcat is not picking it up. Why is it so? 2. When I use tomcat, system property "java.naming.factory.initial" is initialized to "org.apache.naming.java.javaURLContextFactory". Where did the system pick this property from? How can I override this setting? I initialized JNDI context with environment having "java.naming.factory.initial" as "com.sun.enterprise.naming.SerialInitContextFactory" but ultimately "org.apache.naming.java.javaURLContextFactory" is set to "java.naming.factory.initial". How can I avoid this? I would appreciate if anybody can help me with these issues. I am really struggling for a week. tia, Srinivas = I am not afraid of losing. But I don't like it. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath issues and system properties
"srinivas reddy" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > I am using tomcat 4.1.24. I have a couple of > questions. > > 1. Online documentation about class loader says, > System class loader operates on CLASSPATH. I have > included j2ee.jar in my CLASSPATH, but tomcat is not > picking it up. Why is it so? Wherever you saw these docs, they are wrong. Tomcat ignores the CLASSPATH variable. And, in any case, trying to use j2ee.jar with Tomcat is pure evil ;-). Just install the components that you need, and you may finish your project in finite time :). > > 2. When I use tomcat, system property > "java.naming.factory.initial" is initialized to > "org.apache.naming.java.javaURLContextFactory". Where > did the system pick this property from? How can I > override this setting? I initialized JNDI context with > environment having "java.naming.factory.initial" as > "com.sun.enterprise.naming.SerialInitContextFactory" > but ultimately > "org.apache.naming.java.javaURLContextFactory" is set > to "java.naming.factory.initial". How can I avoid > this? I don't believe that you can avoid it (without looking more deeply into the code than I care to do at the moment). And, even if you could, the likely result is that Tomcat would lay on it's back, point it's toes in the air, and die. > > I would appreciate if anybody can help me with these > issues. I am really struggling for a week. > > tia, > Srinivas > > = > I am not afraid of losing. But I don't like it. > > __ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath issues and system properties
--- Bill Barker <[EMAIL PROTECTED]> wrote: > > "srinivas reddy" <[EMAIL PROTECTED]> wrote > in message > news:[EMAIL PROTECTED] > > Hi, > > I am using tomcat 4.1.24. I have a couple of > > questions. > > > > 1. Online documentation about class loader says, > > System class loader operates on CLASSPATH. I have > > included j2ee.jar in my CLASSPATH, but tomcat is > not > > picking it up. Why is it so? > > Wherever you saw these docs, they are wrong. Tomcat > ignores the CLASSPATH > variable. I found this documentation at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html. Did I misunderstand it or it says what I am thinking? > And, in any case, trying to use j2ee.jar > with Tomcat is pure evil > ;-). Just install the components that you need, and > you may finish your > project in finite time :). > Why is using j2ee.jar with tomcat is not recommended? Is there any resource explaining what can go wrong? > > > > 2. When I use tomcat, system property > > "java.naming.factory.initial" is initialized to > > "org.apache.naming.java.javaURLContextFactory". > Where > > did the system pick this property from? How can I > > override this setting? I initialized JNDI context > with > > environment having "java.naming.factory.initial" > as > > > "com.sun.enterprise.naming.SerialInitContextFactory" > > but ultimately > > "org.apache.naming.java.javaURLContextFactory" is > set > > to "java.naming.factory.initial". How can I avoid > > this? > > I don't believe that you can avoid it (without > looking more deeply into the > code than I care to do at the moment). And, even if > you could, the likely > result is that Tomcat would lay on it's back, point > it's toes in the air, > and die. > > > > > I would appreciate if anybody can help me with > these > > issues. I am really struggling for a week. > > > > tia, > > Srinivas > > > > = > > I am not afraid of losing. But I don't like it. > > > > __ > > Do you Yahoo!? > > Yahoo! SiteBuilder - Free, easy-to-use web site > design software > > http://sitebuilder.yahoo.com > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > = I am not afraid of losing. But I don't like it. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: classpath issues and system properties
Howdy, >I found this documentation at >http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html . >Did I misunderstand it or it says what I am thinking? You misunderstood it. >Why is using j2ee.jar with tomcat is not recommended? Because it contains duplicate older versions of certain APIs included and required for tomcat, most especially the servlet API. >Is there any resource explaining what can go wrong? Yes, this list's archives. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath issues and system properties
At 08:48 AM 8/21/2003, you wrote: > > 1. Online documentation about class loader says, > > System class loader operates on CLASSPATH. I have > > included j2ee.jar in my CLASSPATH, but tomcat is > not > > picking it up. Why is it so? > > Wherever you saw these docs, they are wrong. Tomcat > ignores the CLASSPATH > variable. I found this documentation at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html. Did I misunderstand it or it says what I am thinking? What it says is that the System Classloader loads classes from the classpath. This is true. HOWEVER, Tomcat out-of-the-box ignores whatever you set for the CLASSPATH env variable and builds it from scratch in it's stratup scripts. This behavior was not an accident in Tomcat's development. Don't mess with it unless you're fully aware of why and how Tomcat's classloaders work the way they do. STFA for more info on this. justin Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential See http://www.nextengine.com/confidentiality.php - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
