I feel, we tried many combinations to see if it is a configurations issue, but of now use. It seems to be a bug in Tomcat & it is present in all the versions we tried out. We are declaring it as a bug, let us know if any one has any other suggestions/soln to try out.
Thanks in advance, Yogi -----Original Message----- From: Yogi [mailto:[EMAIL PROTECTED] Sent: Thursday, February 03, 2005 7:47 PM To: 'Tomcat Users List' Subject: RE: jspInit() throwing NamingException when extracting a factory object from JNDI context Appreciate if any one has some inputs....We couldn't decide whether it is a bug or usage issue,... Details @ http://issues.apache.org/bugzilla/show_bug.cgi?id=33307 Problem: -------- jspInit() throwing NamingException when extracting a factory object from JNDI context. Description: ------------ When the container has been configured to load the JSP page during startup by including the Load-On-Startup tag in web.xml, the NamingException has been reported( can be viewed in the attachment). The Tomcat Version which we are using is Tomcat 4.1.3. How to Reproduce the problem: ----------------------------- Step 1) create a directory under webapps (say test) and unzip the attached jsppax.zip into the test dir under webapps. Step 2) add the following lines to server.xml <Context path="/test" docBase="d:\jakarta-tomcat-4.1.30\webapps\test" debug="0"/> <!-- DefaultContext --> <DefaultContext reloadable="true" crossContext="true" useNaming="true"> <!-- bean/MyBeanFactory --> <Resource name="bean/MyBeanFactory" auth="Container" type="com.mycompany.MyBean"/> <ResourceParams name="bean/MyBeanFactory"> <parameter> <name>factory</name> <value>org.apache.naming.factory.BeanFactory</value> </parameter> <parameter> <name>bar</name> <value>23</value> </parameter> </ResourceParams> </DefaultContext> <!-- /DefaultContext --> Step 3) start the server During startup, the NamingException has been reported. We tried with couple of other Tomcat versions aswell it is poping that NamingException with them also. Please letus know if you had any issues while reproducing the above exception. You can refer to the bugid :33307 if you need more information. Please let us Know if it is a configuration issue or a bug in JSP-TomCat. Awaiting yor response.. Thanks in Advance Yogi Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]