read it immediately

2004-02-19 Thread cmanolache
i wait for a reply! attachment: party.zip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: all those *-auto files

2001-08-07 Thread cmanolache
On Mon, 6 Aug 2001, Klaas van der Ploeg wrote: It is not yet optional (at least not in 3.2.3), but it is marked in the source with XXX to make it optional. You can comment it out and recompile Tomcat.java if you really want to get rid of those files. It is optional in 3.3 ( and disabled by

Re: Virtual Hosts on IIS Tomcat

2001-08-07 Thread cmanolache
On Fri, 3 Aug 2001, Knaggs, George R wrote: Mr Shachor / Tomcat-User, I hope you don't mind this email but I've been unable to find any information on how to configure IIS with Tomcat using a Virtual Host where the context path / URI is the root (http://one.domain.com/ and

Re: TC3.2.1 - response commit on included JSPs

2001-02-26 Thread cmanolache
" if that destination is another character or byte stream, flush it." In this case, the destination is the servlet output stream - and it has to be flushed. That is only because the particular servlet engine implementation implements the ServletOutputStream of the Response object

Re: TC3.2.1 - response commit on included JSPs

2001-02-23 Thread cmanolache
I won't contest that, but I would suggest considering the idea that the final, or intended destination is not necessarily the browser. In the case of an included resource, it is the calling servlet that is acting as client to the included resource. In good OO design, it should be in the

Re: TC3.2.1 - response commit on included JSPs

2001-02-22 Thread cmanolache
The problem is that flush() must still be executed as expected, i.e. if an included JSP or servlet is actually calling flush(), it expects the response to be commited. But does that necessarily mean to commit it to the browser? Or should it instead just commit it to the buffer

Re: Tomcat3.2 final doesn't support user defined MIME type

2000-12-19 Thread cmanolache
Bug: Tomcat3.2 doesn't support user defined MIME type in added "TOMCAT_HOME\conf\web.xml". Instead, it returns text/plain. You should set the MIME types in the webapplication's web.xml. This has been a source of confusion in the past, and a big mistake - if you want portable web

Re: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread cmanolache
Given that the default web.xml is not being read, how do you enable Jikes as the JspCompiler? That setting used to be in web.xml. What's the syntax to specify it in server.xml, or did we lose this functionality for Tomcat 3.2? (If so, could it be put back, or define a syntax in server.xml

Re: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread cmanolache
Given that the default web.xml is not being read, how do you enable Jikes as the JspCompiler? That setting used to be in web.xml. What's the syntax to specify it in server.xml, or did we lose this functionality for Tomcat 3.2? (If so, could it be put back, or define a syntax in