Yes you can, even if this is not required. If you can't use the standalone HTTP connectors provided in the Noelios Restlet Engine, you can still use the ServerServlet connector which is an adapter between the Servlet API and the Restlet API. See the ServerServlet Javadocs for details on how to configure your Servlet container. Class "com.testServlet.

Error pages are served to Internet users when any one of a variety of errors occur, such as when a user enters an incorrect URL or is not authorized to access a specific directory in your web site. Companies often customize error pages to brand them with a specific corporate image and a link to their home page. You do not have to customize these pages - the error page is always available, whether customized or not. Enter the HTML code for the error page.

When someone visits a website or area there is always a possibility that the link they followed may be out-of-date or broken or they may have typed the address in wrongly. When this happens an error page is displayed. By default a standard error page is received. This does not give the user much information about the area they were in or any details of who they should contact. A custom error page allows you to specify a set of links the visitor could try, as well as a contact for help.

Yes, we can support Custom Error pages. These pages enable you to specify a page on your web site that a user will see if they are presented with errors, such as 'The page cannot be found' or 'You are not authorised to view this page'. For example, to keep visitors on your web site you could present them with a 'Site Map' page when they mistype a URL or encounter a broken link.

Yes. Just click the Error Pages icon on your Control Panel to quickly create a custom page for any of the following situations:

Yes, you can use the .htaccess file to define your error pages. If you need further assistance get in touch and we will be more than happy to help you set this feature up.

Author: Sylvain GIBIER (http://www.jguru.com/guru/viewbio.jsp?EID=11408) Question originally posed by Arnar Freyr Guðmundsson (http://www.jguru.com/guru/viewbio.jsp?EID=26079 Look at the Tomcat IIS How to file located at the address : http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/tomcat-iis-howto.html (or http://jakarta.apache.org/cvsweb/index.cgi/jakarta-tomcat/etc/tomcat-iis-howto.html if the website version is out of date).

Also refer to the recently published article at Use Microsoft's Internet Information Server as a Java servlet engine

Author: David Garcia (http://www.jguru.com/guru/viewbio.jsp?EID=17915) Question originally posed by Graham Lea (http://www.jguru.com/guru/viewbio.jsp?EID=101834 I'm not sure about Tomcat but in WebLogic (from 4.0.2 to 5.1 versions) there is parameter in the weblogic.properties file which can enable (or disable) cookies. in server.xml, you need to create a Context entry for your web app and add: cookies="false" in order for it to not use cookies by default.

Author: Avi Kak (http://www.jguru.com/guru/viewbio.jsp?EID=26410) The "invoker servlet" is a system-supplied servlet that extracts the name of the requested servlet class from the portion of the URL that comes after "/servlet". The invoker servlet then loads the requested servlet into the container and executes it. If you look at the contents of the webapp deployment descriptor file, web.

Author: Serge Knystautas (http://www.jguru.com/guru/viewbio.jsp?EID=100012) Question originally posed by Felix Wong (http://www.jguru.com/guru/viewbio.jsp?EID=102927 Servlet aliasing is a two part process with Apache and Tomcat. First, you must map the request in Apache to Tomcat with the ApJServMount directive, e.g., ApJServMount /myservlet /ROOT Second, you must map that url pattern to a servlet name and then to a servlet class in your web.xml configuration file.

Author: Alex Chaffee (http://www.jguru.com/guru/viewbio.jsp?EID=3) Question originally posed by Prashant Kumashi (http://www.jguru.com/guru/viewbio.jsp?EID=293844 Not yet. The next version (2.3) of the Servlet Spec will allow something like servlet chaining. It's called "filters." Can I use a Generic SAX/DOM XML parser for Tomcat instead of parser.jar? I tried using Xerces and get class not found errors for sun.xxxx parser during Tomcat initialization.

Sure, you can. "ProSubmitter?" can harvest URLs from Google, Yahoo and MSN listings. There is also a module for editing new forms with which you can set up submitting to other site types.

Yes you can set several custom error pages through your control panel, so if a customer tries a page that no longer exists they can be redirected to your main web site instead of getting a generic error.