Exception management in servlet listeners

[Heligon Sandra <sa...@nextream.fr>]

I use the new feature ServletContextListener of the Servlet specifications
2.3. 
I defined the following class: 
public final class XSS_ServletContextListener implements
ServletContextListener { 
	private static ServletContext s_context = null; 
	public void contextInitialized(ServletContextEvent arg0) {
	 s_context = arg0.getServletContext(); 
	try{ // Get the reference on a CORBA object reference 
		SessionManager sessionManager =
SessionManager.getSingleInstance(); ... 
	} 
	catch (ExBadManagerName ex) 
	{ } 
} 
I don't what to do when the exception ExBadManagerName occurs. I am trying
to define in the web.xml file of my application the following element 
<error-page> 
	<exception-type>com.mycompagny.ExBadManagerName </exception-type> 
	<location>/pages/errorPage.jsp</location> 
</error-page> 
but the page is not displayed. 
What can I do to inform the client if an exception occurs, the index.jsp
page of my application has not to be displayed. 
Thanks a lot in advance 




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

tomcat 4.1 does not resolve links

[Alexander Piavka <pi...@cs.bgu.ac.il>]

 Hello, i'm using tomcat 4.1.12 and i found that tomcat does not follow
symbolic links under the application context.
If i define some context and copy to the application space some jsp file
it works, but if instead i make link to it(the file is located on another
nfs mounted partition) i get the messaage:

HTTP Status 404 - /zopa.jsp
 type Status report
 message /zopa.jsp
 description The requested resource (/zopa.jsp) is not available.

while in previous version of tomcat-4.0 the symbolic links work.

Is there some way to make tomcat 4.2 follow symbolic links, or this
feature was disabled on purpose?

 Thanks a lot.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>