[Coyote] Coyote 1.0 Beta 2 available
Coyote 1.0 Beta 3 is now available, and includes: - A high performance HTTP/1.1 processor - An adapter for Tomcat 3.3.x - An adapter for Tomcat 4.0.x - URL normalization in the Tomcat 4 adapter, to prevent URL based security attacks - Support HTTP/1.1 expectations (requires Tomcat 4 nightly builds) Binaries can be downloaded at: http://jakarta.apache.org/builds/jakarta-tomcat-connectors/coyote/release/v1 .0-b3/ Installation instructions for both 3.3.x and 4.0.x are given on the download page. The Tomcat 4 nighly builds already include this new connector. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7173] New: - Tomcat fails to respect HTTP HEAD request
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7173. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7173 Tomcat fails to respect HTTP HEAD request Summary: Tomcat fails to respect HTTP HEAD request Product: Tomcat 4 Version: 4.0.3 Final Platform: Other OS/Version: Linux Status: NEW Severity: Minor Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Where to send code?
Hi all! I'll write a modification of the manager servlets that allows you to manage an entire Engine throught only one instance of the manager and I transtaled to spanish the localstrings. But I don't know where to send this changes for crontibuting them to the project. Meanwhile I'll posted them at my website www.talika.org if anyone want to see it. - Jose M. Palomar www.talika.org -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/config context.xml
craigmcc02/03/16 12:32:31 Modified:webapps/tomcat-docs jndi-resources-howto.xml webapps/tomcat-docs/config context.xml Log: Document the configuration properties for the COMMONS-DBCP-based data source factory in the HEAD branch. Revision ChangesPath 1.13 +36 -1 jakarta-tomcat-4.0/webapps/tomcat-docs/jndi-resources-howto.xml Index: jndi-resources-howto.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/jndi-resources-howto.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- jndi-resources-howto.xml 13 Mar 2002 04:13:34 - 1.12 +++ jndi-resources-howto.xml 16 Mar 2002 20:32:31 - 1.13 @@ -515,9 +515,17 @@ lt;valuegt;org.hsql.jdbcDriverlt;/valuegt; lt;/parametergt; lt;parametergt; - lt;namegt;driverNamelt;/namegt; + lt;namegt;urllt;/namegt; lt;valuegt;jdbc:HypersonicSQL:databaselt;/valuegt; lt;/parametergt; +lt;parametergt; + lt;namegt;maxActivelt;/namegt; + lt;valuegt;8lt;/valuegt; +lt;/parametergt; +lt;parametergt; + lt;namegt;maxIdlelt;/namegt; + lt;valuegt;4lt;/valuegt; +lt;/parametergt; lt;/ResourceParamsgt; ... lt;/Contextgt; @@ -530,6 +538,33 @@ JDBC driver. Customize the codedriverClassName/code and codedriverName/code parameters to match your actual database's JDBC driver and connection URL./p + +pThe configuration properties for Tomcat's standard data source +resource factory +(codeorg.apache.naming.factory.DbcpDataSourceFactory/code) are +as follows:/p +ul +listrongdriverClassName/strong - Fully qualified Java class name +of the JDBC driver to be used./li +listrongmaxActive/strong - The maximum number of active instances +that can be allocated from this pool at the same time./li +listrongmaxIdle/strong - The maximum number of connections that +can sit idle in this pool at the same time./li +listrongmaxWait/strong - The maximum number of milliseconds that the +pool will wait (when there are no available connections) for a +connection to be returned before throwing an exception./li +listrongpassword/strong - Database password to be passed to our +JDBC driver./li +listrongurl/strong - Connection URL to be passed to our JDBC driver. +(For backwards compatibility, the property codedriverName/code +is also recognized.)/li +listronguser/strong - Database username to be passed to our +JDBC driver./li +listrongvalidationQuery/strong - SQL query that can be used by the +pool to validate connections before they are returned to the +application. If specified, this query MUST be an SQL SELECT +statement that returns at least one row./li +/ul /subsection 1.8 +1 -1 jakarta-tomcat-4.0/webapps/tomcat-docs/config/context.xml Index: context.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/config/context.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- context.xml 30 Nov 2001 06:23:13 - 1.7 +++ context.xml 16 Mar 2002 20:32:31 - 1.8 @@ -601,7 +601,7 @@ lt;valuegt;org.hsql.jdbcDriverlt;/valuegt; lt;/parametergt; lt;parametergt; - lt;namegt;driverNamelt;/namegt; + lt;namegt;urllt;/namegt; lt;/valuegt;jdbc:HypersonicSQL:databaselt;/valuegt; lt;/parametergt; lt;parametergt; -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] New: - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser Summary: Class loading issues when using own XML parser Product: Tomcat 4 Version: 4.0.4 Beta 1 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Starting from Tomcat 4.0.2, it is not possible to bundle web applocation with the XML parser of choice. If application ships with the parser in the WEB- INF/lib, following exception occurs: --8- java.lang.ClassCastException: org.apache.xerces.parsers.StandardParserConfiguration at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(Unknown Source) at org.apache.jsp.test$jsp._jspService(test$jsp.java:71) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:202) ... --8- How to reproduce: 1. Create empty webapp (or use existing, like ROOT) 2. Drop xercesImpl-2.0.0.jar and xml-apis.jar into WEB-INF/lib. 3. Create test.jsp (attached) 4. Invoke test.jsp -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 21:58 --- Created an attachment (id=1357) test.jsp -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |High --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 22:02 --- xml-apis.jar: http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-cocoon2/lib/core/xml-apis.jar? rev=1.3content-type=text/plain xercesImpl-2.0.0.jar: http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-cocoon2/lib/core/xercesImpl- 2.0.0.jar?rev=1.1content-type=text/plain -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7008] - facade.HttpServletRequestFacade.getParameter(HttpServletRequestFacade.java:277) -- java.lang.ArrayIndexOutOfBoundsException
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7008. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7008 facade.HttpServletRequestFacade.getParameter(HttpServletRequestFacade.java:277) -- java.lang.ArrayIndexOutOfBoundsException [EMAIL PROTECTED] changed: What|Removed |Added Severity|Blocker |Major --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 22:36 --- Thanks. http Ethereal log: GET /myapp/servlet/ HTTP/1.1 Accept: */* Referer: http://montpellier/myapp/servlet/myservlet?search=listCodes=listCommunes=listAdresses=listnumberCodes=listnumberCommunes=listnumberAdresses=cb_searchVoie=falsecb_searchProche=falsecb_num=truecb_bister=truecb_typeVoie=falsecb_voie=truecb_codePostal=truecb_commune=falseccb_num=onccb_bister=onccb_voie=onccb_codePostal=onnum=12bister=typeVoie=voie=DE+L+EUROPE+PARC+GUSTAVE+EIFFELcodePostal=77600commune=LYOlistesCodes=chercherCommune=Chercher+avec+la+communerafraichirCarte=data=outil=donnees=x=y=ortho=falseraster=trueparcelles=truebatiments=truearbres=trueclutter1=falseclutter4=falsex_terrain=y_terrain=commentaire=cb_arbres=truecb_parcelles=truecb_batiments=truecb_raster=true Accept-Language: fr Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt) Host: montpellier Connection: Keep-Alive Cookie: JSESSIONID=in2xlk7af1 HTTP/1.1 404 Introuvable Date: Sat, 16 Mar 2002 12:11:12 GMT Server: Apache/1.3.22 (Win32) mod_jk/1.1.0 Content-Length: 193 Servlet-Engine: Tomcat Web Server/3.3.1 Release Candidate 1 ( JSP 1.1; Servlet 2.2 ) Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Content-Type: text/html headtitleIntrouvabble(404)/title/head bodyh1Introuvabble(404)/h1 Requête originale: /myapp/servlet/ brbr bRequête introuvable:/b /myapp/servlet/ /body GET /myapp/servlet/myservlet?search=listCodes=listCommunes=70313+69381+69382+69383+69384+69385+69386+69387+69388+69389+27377+70004+70014+70021+70029+70046+70081+70157+70161+70178+70195+70229+70250+70254+70259+70260+70294+70304+70306+70310+70318+70319+70321+70328+70348+70385+70403+70432+70445+70455+70464+70515+70544+70577+70581+69381+69382+69383+69384+69385+69386+69387+69388+69389+69387+69381+69382+69383+69384+69385+69386+69387+69388+69389+69382+69387+38926+69299+27048+27066+27094+27245+27369+27373+27664+listAdresses=listnumberCodes=listnumberCommunes=0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23+24+25+26+27+28+29+30+31+32+33+34+35+36+37+38+39+40+41+42+43+44+45+46+47+48+49+50+51+52+53+54+55+56+57+58+59+60+61+62+63+64+65+66+67+68+69+70+71+72+73+74+listnumberAdresses=cb_searchVoie=falsecb_searchProche=falsecb_num=truecb_bister=truecb_typeVoie=falsecb_voie=truecb_codePostal=truecb_commune=falseccb_num=onccb_bister=onccb_voie=onccb_codePostal=onnum=12bister=typeVoie=voie=DE+L+EUROPE+PARC+GUSTAVE+EIFFELcodePostal=77600commune=LYOlistesCodes=chercherCommune=Chercher+avec+la+communelistesCommunes=70313listesCommunes=69381listesCommunes=69382listesCommunes=69383listesCommunes=69384listesCommunes=69385listesCommunes=69386listesCommunes=69387listesCommunes=69388listesCommunes=69389listesCommunes=27377listesCommunes=70004listesCommunes=70014listesCommunes=70021listesCommunes=70029listesCommunes=70046listesCommunes=70081listesCommunes=70157listesCommunes=70161listesCommunes=70178listesCommunes=70195listesCommunes=70229listesCommunes=70250listesCommunes=70254listesCommunes=70259listesCommunes=70260listesCommunes=70294listesCommunes=70304listesCommunes=70306listesCommunes=70310listesCommunes=70318listesCommunes=70319listesCommunes=70321listesCommunes=70328listesCommunes=70348listesCommunes=70385listesCommunes=70403listesCommunes=70432listesCommunes=70445listesCommunes=70455listesCommunes=70464listesCommunes=70515listesCommunes=70544listesCommunes=70577listes HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* Referer: http://montpellier/myapp/servlet/myservlet?search=listCodes=listCommunes=listAdresses=listnumberCodes=listnumberCommunes=listnumberAdresses=cb_searchVoie=falsecb_searchProche=falsecb_num=truecb_bister=truecb_typeVoie=falsecb_voie=truecb_codePostal=truecb_commune=falseccb_num=onccb_bister=onccb_voie=onccb_codePostal=onnum=12bister=typeVoie=voie=DE+L+EUROPE+PARC+GUSTAVE+EIFFELcodePostal=77600commune=LYOlistesCodes=chercherCommune=Chercher+avec+la+communerafraichirCarte=data=outil=donnees=x=y=ortho=falseraster=trueparcelles=truebatiments=truearbres=trueclutter1=falseclutter4=falsex_terrain=y_terrain=commentaire=cb_arbres=truecb_parcelles=truecb_batiments=truecb_raster=true Accept-Language: fr Accept-Encoding:
DO NOT REPLY [Bug 7173] - Tomcat fails to respect HTTP HEAD request
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7173. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7173 Tomcat fails to respect HTTP HEAD request [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 22:41 --- You'll have to provide an example of bad behavior, as this is a duplicate of bug 5126, which was fixed. *** This bug has been marked as a duplicate of 5126 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5126] - Client request using HEAD results in a response body returned to client.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5126. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5126 Client request using HEAD results in a response body returned to client. [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 22:41 --- *** Bug 7173 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7176] New: - Servlet API error: sendError with commited buffer - java.lang.Throwable: Trace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7176. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7176 Servlet API error: sendError with commited buffer - java.lang.Throwable: Trace Summary: Servlet API error: sendError with commited buffer - java.lang.Throwable: Trace Product: Tomcat 3 Version: 3.3.1 Release Candidate 1 Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: Other Component: Servlet AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Effect: stop tomcat. it's dealing with .jsp include and usebean. - Ctx(/myapp) : Servlet API error: sendError with commited buffer - java.lang.Throwable: Trace at org.apache.tomcat.facade.HttpServletResponseFacade.sendError(HttpServletRe sponseFacade.java:213) at org.apache.tomcat.facade.HttpServletResponseFacade.sendRedirect(HttpServle tResponseFacade.java:240) at jsp.onglets_2._jspService(onglets_2.java:105) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574) at org.apache.tomcat.core.Handler.invoke(Handler.java:322) at org.apache.tomcat.core.Handler.service(Handler.java:235) at org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485) at org.apache.tomcat.facade.RequestDispatcherImpl.doInclude(RequestDispatcher Impl.java:402) at org.apache.tomcat.facade.RequestDispatcherImpl.include(RequestDispatcherIm pl.java:189) at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:413 ) at jsp.suividemandes.saisie.main_4._jspService(main_4.java:85) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574) at org.apache.tomcat.core.Handler.invoke(Handler.java:322) at org.apache.tomcat.core.Handler.service(Handler.java:235) at org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java: 917) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:833) at org.apache.tomcat.modules.server.Ajp12Interceptor.processConnection(Ajp12I nterceptor.java:208) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.j ava:516) at java.lang.Thread.run(Thread.java:484) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 23:12 --- I don't agree with this bug report, and I tried the test case just to be sure. This does work for both the HEAD branch and 4.0.4-dev (which should be identical to 4.0.4-b1). 4.0.2 and 4.0.3 should also work fine (but I didn't try). If you still have problems, I would recommend stopping to attempt to override the XML parser altogether, as because of the CL delegation model used by the servlet API, this cannot be supported in a robust way. So you get to choose between WORKSFORME or WONTFIX for the resolution of the bug. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 23:24 --- I agree with Remy that you should stop trying to override the default XML parser. While you *may* be able to override it when using JDK 1.3, you will absolutely not be able to do it with JDK 1.4 as JDK 1.4 treats the XML parsing classes (also known as endorsed classes) as system classes. Hence, once the JVM is started, JDK 1.4 will not all any class loader in the process load alternate XML parsing classes that fall in any package names listed in the following URL: http://java.sun.com/j2se/1.4/docs/guide/standards/index.html The only way around this JDK 1.4 restriction for your webapp only is to create an XML parser with package names that are not listed in the above URL (i.e. a very non-standard parser). There is another way around this restriction. However, it will force all webapps (and the container itself) to use your XML parser. You can put your parser jar files in the common/lib directory (4.0.x) or in the common/endorsed directory (HEAD). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME | --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 23:34 --- Let take this one step at a time. What do you mean under you should stop trying to override the default XML parser? If it is equivalent to the properties.put (org.xml.sax.driver, org.apache.xerces.parsers.SAXParser); in the test.jsp, I would have anything against this if it would work. However, reality is worse than that, and if I remove the line, I end up with another exception: 8- org.xml.sax.SAXException: System property org.xml.sax.driver not specified at org.xml.sax.helpers.XMLReaderFactory.createXMLReader (XMLReaderFactory.java:90) at org.apache.jsp.test2$jsp._jspService(test2$jsp.java:65) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service (JspServlet.java:202) 8- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 23:35 --- Created an attachment (id=1358) test.jsp without properties.put line -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 23:48 --- As I have said (did you actually read my reply ?), I tried the first JSP against both TC braches, and it *did* work (both with JDK 1.3 and 1.4), and your test displayed Passed. TC 4.0.4-dev; Xeces 1.4.4 in common/lib; Xerces 2.0.0 in /webapps/ROOT/WEB-INF/lib; test.jsp in /webapps/ROOT/test.jsp As Patrick stated, overriding the XML parser can be considered unsupported functionality. So if it didn't work, there's nothing I can do to fix it, and this is a WONTFIX. If you think you can fix it, I'm waiting for your patch (but the catch is that it still must implement the delegation model specified by the servlet API) ;-) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: setting up tomcat to accept client certificate
Hi, Whenever I try to set the parameter clientAuth=true in the server.xml to accept client certificate from the user, after restarting Tomcat starts up well, but then I get 'Cannot find server' error when I try to access the https sites. But the http sites work perfectly. But when this parameter is set to 'false' https and http both works perfectly, though the client is not asked for certificate. The server certificate I am using has been generated by keytool. The client certificate is a third party one. I am using Tomcat standalone version 4.0.1 with jdk1.3.1 I have downloaded the jsse1.0.2 and put the 3 jar files in the jdk ext path. Any pointer will be really helpful. We're using client auth in our application and here's how we got it working (Linux 2.4/Windows NT/Windows 2000, Sun Jdk 1.3.1_02/IBM JDK 1.3): - The key store used when validating client certs against CA certs is JAVA_HOME/jre/lib/security/cacerts - Delete all unwanted CA certs from this keystore (usually all of them). - Add the required CA certs. - Client auth should now work fine. This solution has the problem that it affects all Java programs using JSSE. That's not an issue in our environment, but it may be in your's. Maybe an SSL specialist knows a little more about this (Erik?). BTW, I didn't see anything about this in the docs (though I haven't looked at them for quite a while). If it's not there, it should be added. Of course, a clean solution that only affects individual webapps would be better. Does it help using PureTLS? Best regards Andreas Junghans -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser --- Additional Comments From [EMAIL PROTECTED] 2002-03-16 23:53 --- Yes, Remy, I have read your reply. And yes, the test case as I submitted - works: I installed fresh Tomcat and found that it is working. The things are becoming interesting (i.e. test case does not work) when xerces.jar is removed from the tomcat/commoon/lib, and instead of it two mentioned jars (xml-apis.jar and xerces.jar) are copied to the tomcat/common/lib. When Tomcat and webapp uses same libs, the issue I was describing arises. Could you please give your comment on this? Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources FileDirContext.java
remm02/03/16 16:03:13
Modified:catalina/src/share/org/apache/naming/resources
FileDirContext.java
Log:
- Fix an off-by-one bug in the canonicalization code. Somehow it was failing only
on JDK 1.3, but not on 1.4.0, and somehow 4.0.x works fine (so I don't plan to fix
it).
Revision ChangesPath
1.13 +8 -16
jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/FileDirContext.java
Index: FileDirContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/FileDirContext.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- FileDirContext.java 14 Mar 2002 20:55:47 - 1.12
+++ FileDirContext.java 17 Mar 2002 00:03:13 - 1.13
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/FileDirContext.java,v
1.12 2002/03/14 20:55:47 remm Exp $
- * $Revision: 1.12 $
- * $Date: 2002/03/14 20:55:47 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/FileDirContext.java,v
1.13 2002/03/17 00:03:13 remm Exp $
+ * $Revision: 1.13 $
+ * $Date: 2002/03/17 00:03:13 $
*
*
*
@@ -99,7 +99,7 @@
* Filesystem Directory Context implementation helper class.
*
* @author Remy Maucherat
- * @version $Revision: 1.12 $ $Date: 2002/03/14 20:55:47 $
+ * @version $Revision: 1.13 $ $Date: 2002/03/17 00:03:13 $
*/
public class FileDirContext extends BaseDirContext {
@@ -854,15 +854,6 @@
*/
protected File file(String name) {
-/*
-name = normalize(name);
-if (name == null)
-return (null);
-
- if (File.separatorChar == '\\')
-name = name.replace('/', File.separatorChar);
-*/
-
File file = new File(base, name);
if (file.exists() file.canRead()) {
@@ -875,8 +866,9 @@
if (canPath == null)
return null;
-if (!canPath.startsWith(absoluteBase))
+if (!canPath.startsWith(absoluteBase)) {
return null;
+}
// Windows only check
if ((caseSensitive) (File.separatorChar == '\\')) {
@@ -888,12 +880,12 @@
canPath = normalize(canPath);
if ((absoluteBase.length() absPath.length())
(absoluteBase.length() canPath.length())) {
-absPath = absPath.substring(absoluteBase.length());
+absPath = absPath.substring(absoluteBase.length() + 1);
if ((canPath == null) || (absPath == null))
return null;
if (absPath.equals())
absPath = /;
-canPath = canPath.substring(absoluteBase.length());
+canPath = canPath.substring(absoluteBase.length() + 1);
if (canPath.equals())
canPath = /;
if (!canPath.equals(absPath))
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7175] - Class loading issues when using own XML parser
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7175 Class loading issues when using own XML parser --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 00:15 --- I tried only with 4.0.4-dev (ran into another bug with HEAD and JDK 1.3). If I replace Xerces 1.4.4 with Xerces 2.0.0 in common/lib, cleanup the work directory, it still does work on both JDK 1.3 and 1.4. I don't understand why it would fail. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7177] New: - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem Summary: Apache/mod_jk/Tomcat Connectivity Problem Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: JK/AJP Connector AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm using Apache 1.3.19, mod_jk, and Tomcat 4.0.3. Over time, Tomcat and Apache hang. Both must be restarted to correct the problem. I believe the problem lies in the mod_jk connector and the Ajp13 connector in Tomcat. We have a high-traffic server, and I see quite a few errors in both the mod_jk and Catalina logs. Any insight into this would be helpful - you'll notice that catalina has created it's 74th background thread for the ajp13 connector - I have a max of 75 processors. I don't know if those two are related, but I may be approaching a hang... JC My server.xml configuration at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) 2002-03-15 20:16:21 Ajp13Processor[8009][20] process: invoke java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse (Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) 2002-03-15 20:16:32 Ajp13Processor[8009][46] process: invoke java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse (Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) 2002-03-15 21:06:39 Ajp13Processor[8009][20] process: invoke java.io.IOException: Connection reset by peer at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse (Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) 2002-03-15 21:07:32 Ajp13Processor[8009][6] process: invoke java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse (Ajp13Response.java:192) at org.apache.ajp.tomcat4.Ajp13Processor.process (Ajp13Processor.java:435) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:536) 2002-03-15 21:07:36 Ajp13Processor[8009][20] process: invoke java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
DO NOT REPLY [Bug 7177] - Apache/mod_jk/Tomcat Connectivity Problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 02:50 --- what version of mod_jk are you using? it appears to be an older version, which probably won't work with the ajp connector in tc4. the fact that the latest version of jk_ajp13_worker.c (which doesn't appear to have been changed since early december 2001) has only 145 lines and you are seeing messages like the one below is what leads me to believe you are using an old version of mod_jk. [Sat Mar 16 14:12:59 2002] [jk_ajp13_worker.c (381)]: Error ajp13_process_callback - write failed -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7008] - facade.HttpServletRequestFacade.getParameter(HttpServletRequestFacade.java:277) -- java.lang.ArrayIndexOutOfBoundsException
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7008. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7008 facade.HttpServletRequestFacade.getParameter(HttpServletRequestFacade.java:277) -- java.lang.ArrayIndexOutOfBoundsException [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 03:00 --- This is fixed in the nightly, and will appear in 3.3.1 Final. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7176] - Servlet API error: sendError with commited buffer - java.lang.Throwable: Trace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7176. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7176 Servlet API error: sendError with commited buffer - java.lang.Throwable: Trace [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 03:14 --- This is exactly the behavior specified in section 6.1 (or alternatively 8.3 since you're violating both) of the servlet spec. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7170] - JDBCStore don't work with Orcale 8.x
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7170. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7170 JDBCStore don't work with Orcale 8.x --- Additional Comments From [EMAIL PROTECTED] 2002-03-17 04:42 --- Created an attachment (id=1359) Patch of org.apache.catalina.session.JDBCStore. Fix the invalid GROUP-BY expression some NullPointerExceptions -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7179] New: - SaxParser croaking on load-on-startup
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7179. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7179 SaxParser croaking on load-on-startup Summary: SaxParser croaking on load-on-startup Product: Tomcat 4 Version: 4.0.1 Final Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Webapps AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] See web.xml file below. Apache fails to start the web app unless the load-on- startup tag set is removed. load-on-startup is a valid tag in that position per the specification. ---web.xml ?xml version=1.0? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; web-app servlet servlet-nameJCVSServlet/servlet-name display-namejCVS Servlet/display-name servlet-classcom.ice.jcvslet.JCVSlet/servlet-class load-on-startup1/load-on-startup init-param param-nameJCVSletConfigDirectory/param-name param-valueWEB-INF/conf/param-value /init-param init-param param-nameJCVSletTempDirectory/param-name param-valueWEB-INF/temp/param-value /init-param init-param param-nameJCVSletWorkDirectory/param-name param-valueWEB-INF/work/param-value /init-param /servlet servlet-mapping servlet-nameJCVSServlet/servlet-name url-pattern/JCVSlet/*/url-pattern /servlet-mapping /web-app -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util/buf ByteChunk.java
And Craig thought it was a strange world when he contributed to j-t-c. ;-) - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 15, 2002 11:47 PM Subject: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util/buf ByteChunk.java remm02/03/15 23:47:33 Modified:src/share/org/apache/tomcat/util/buf ByteChunk.java Log: - Port indexOf patch to 3.3. Feel free to -1. Revision ChangesPath -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3 CoyoteProcessor.java CoyoteRequest.java CoyoteResponse.java
billbarker02/03/16 21:26:20
Modified:coyote/src/java/org/apache/coyote/tomcat3
CoyoteProcessor.java CoyoteRequest.java
CoyoteResponse.java
Log:
Comment changes only. No functional changes.
Revision ChangesPath
1.5 +23 -0
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3/CoyoteProcessor.java
Index: CoyoteProcessor.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3/CoyoteProcessor.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- CoyoteProcessor.java 16 Mar 2002 04:47:30 - 1.4
+++ CoyoteProcessor.java 17 Mar 2002 05:26:20 - 1.5
@@ -75,6 +75,13 @@
import org.apache.coyote.Adapter;
import org.apache.coyote.Processor;
+/** Per-Thread Adapter between Coyote and Tomcat.
+ * This class handles the task of passing of an individual request to
+ * Tomcat to handle. Also some of the connection-specific methods are
+ * delegated to here.
+ * @Author Bill Barker
+ */
+
class CoyoteProcessor implements Adapter {
private CoyoteRequest reqA;
private CoyoteResponse resA;
@@ -90,18 +97,31 @@
cm.initRequest( reqA, resA );
}
+/** Release resources.
+ */
public void recycle() {
secure = false;
sslImplementation=null;
sslSupport=null;
}
+/** Set the configured SSLImplementation.
+ * @param ssl The SSL Implementation instance.
+ */
public void setSSLImplementation(SSLImplementation ssl) {
sslImplementation = ssl;
}
+
+/** Set the SSL flag.
+ * @param isSecure Is this a secure connection.
+ */
public void setSecure(boolean isSecure) {
secure = isSecure;
}
+
+/** Set the per-socket properties.
+ * @param socket The socket that this Thread is using.
+ */
public void setSocket(Socket socket) {
reqA.setSocket(socket);
if( secure ) {
@@ -110,6 +130,9 @@
sslSupport = sslImplementation.getSSLSupport(socket);
}
}
+
+/** Pass off an individual request to Tomcat.
+ */
public void service(org.apache.coyote.Request request,
org.apache.coyote.Response response)
throws Exception{
1.7 +20 -1
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3/CoyoteRequest.java
Index: CoyoteRequest.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3/CoyoteRequest.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- CoyoteRequest.java16 Mar 2002 05:03:03 - 1.6
+++ CoyoteRequest.java17 Mar 2002 05:26:20 - 1.7
@@ -75,6 +75,11 @@
import org.apache.coyote.Adapter;
import org.apache.coyote.Processor;
+/** The Request to connect with Coyote.
+ * This class handles the I/O requirements and transferring the request
+ * line and Mime headers between Coyote and Tomcat.
+ * @Author Bill Barker
+ */
class CoyoteRequest extends Request {
org.apache.coyote.Request coyoteRequest=null;
@@ -104,6 +109,10 @@
end=-1;
}
+/** Attach the Coyote Request to this Request.
+ * This is currently set pre-request to allow copying the request
+ * attributes to the Tomcat attributes.
+ */
public void setCoyoteRequest(org.apache.coyote.Request cReq) {
coyoteRequest=cReq;
// This is really ugly, but fast.
@@ -125,11 +134,14 @@
scookies.setHeaders(headers);
params.setHeaders(headers);
}
-
+/** Set the socket for this request.
+ */
public void setSocket(Socket socket) {
this.socket = socket;
}
+/** Read a single character from the request body.
+ */
public int doRead() throws IOException {
if( available == 0 )
return -1;
@@ -144,6 +156,8 @@
return readBuffer[pos++] 0xFF;
}
+/** Read a chunk from the request body.
+ */
public int doRead(byte[] b, int off, int len) throws IOException {
if( available == 0 )
return -1;
@@ -183,6 +197,9 @@
}
+/** Determine the local virual host and port from the codehost/code
+ * header.
+ */
protected void parseHostHeader() {
MessageBytes hH=getMimeHeaders().getValue(host);
serverPort = socket.getLocalPort();
@@ -243,6 +260,8 @@
return serverPort;
}
+/** Define the SSL Support support instance for this socket.
+ */
void setSSLSupport(SSLSupport
