Help with Connector API
Hi, I am using embedded tomcat and using API's to create a Connector. The Connector API has public void *setAttribute*(java.lang.String name, java.lang.Object value) also setters for properties e.g) public void *setMaxPostSize* (int maxPostSize) If i use setAttribute for maxPostSize it gets set in Http11ProtocolHandler and if i use setMaxPostSize gets set in Connector. Which is the correct way to set these properties using setAttribute or setter methods for the properties? Does setting it in Http11ProtocolHandler affect the functionality of the property? Regards Krish
Re: Relation of jasper and servlet API to Tomcat
If you want to include the real tomcat in gentoo - please use the official label, follow the same procedure as our release, and make sure the result of emerge is identical with what the user would get if he would get tomcat from ASF. If you have to patch - and the patch alters the structure or behavior - please don't call the result 'tomcat' :-) Costin On 8/19/06, William L. Thomson Jr. [EMAIL PROTECTED] wrote: Tim, Thank you very much for the info. For now at least I will make sure our Jasper package is kept in sync with Tomcat releases. On Sat, 2006-08-19 at 19:36 -0400, Tim Funk wrote: In different versions of Tomcat, Jasper could change a lot since its not a public api. But it's cool for other apps to use it right? It seems Jetty uses Tomcat's Jasper. The servlet api could also change in different Tomcat revisions too. But these changes are usually VERY minor and due to corrections/errata found in the spec. Ok, might just revision bump it as well with Tomcat to be safe, or go monitor the spec changes and etc :) Typically - when Tomcat changes - there was usually a change in Jasper too. So any Tomcat release would require a Jasper release. But there might or might NOT be a servlet api change. Great, that at least gives me some idea of how to maintain those other packages. It seems that Jasper will always be somewhat bound to Tomcat. So no hope of it being packaged or etc on it's own. Hopefully servlet api can, because in 2.4's case it seems to be the only available much less open source implementation. Allot of packages use it. -- William L. Thomson Jr. Gentoo/Java
DO NOT REPLY [Bug 40252] - Different commons-logging version in web app preventing tomcat startup
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40252. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=40252 --- Additional Comments From [EMAIL PROTECTED] 2006-08-20 23:37 --- This is caused by a change in the way commons-beanutils (required by commons-digester) creates objects. It now does things per classloader in some cases and this causes the conflict in commons-logging when it tries to create its logger. I am pursuing a fix with the commons-beanutils team but for now I am going to revert to commons-beanutils 1.6.1 for TC 4.1.33. Votes and time permitting, a release will follow soon. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r433094 - in /tomcat/container/branches/tc4.1.x: RELEASE-NOTES-4.1.txt build.properties.default
Author: markt
Date: Sun Aug 20 17:02:52 2006
New Revision: 433094
URL: http://svn.apache.org/viewvc?rev=433094view=rev
Log:
Fix bug 40252 (commons-logging conflict) by reverting to beanutils 1.6.1
Modified:
tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
tomcat/container/branches/tc4.1.x/build.properties.default
Modified: tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt
URL:
http://svn.apache.org/viewvc/tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt?rev=433094r1=433093r2=433094view=diff
==
--- tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt (original)
+++ tomcat/container/branches/tc4.1.x/RELEASE-NOTES-4.1.txt Sun Aug 20 17:02:52
2006
@@ -146,10 +146,14 @@
[4.1.32] JUnit
Upgrade to 3.8.2
-
[4.1.32] Pure TLS
Upgrade to 0.9b5
+[4.1.33] Commons Collections
+ Upgrade to 3.2
+
+[4.1.33] Commons BeanUtils
+ Revert to 1.6.1
-
@@ -1610,6 +1614,13 @@
[4.1.32] #39769
StandardWrapper
Ensure correct context classloader when calling destroy()
+
+[4.1.33] #40252
+ Commons Logging
+ Revert to Commons BeanUtils 1.6.1 since 1.7.0 introduced an issue
+ that prevented web applications from loading if the Commons Logging
+ library was present in the web application.
+
Coyote Bug Fixes:
Modified: tomcat/container/branches/tc4.1.x/build.properties.default
URL:
http://svn.apache.org/viewvc/tomcat/container/branches/tc4.1.x/build.properties.default?rev=433094r1=433093r2=433094view=diff
==
--- tomcat/container/branches/tc4.1.x/build.properties.default (original)
+++ tomcat/container/branches/tc4.1.x/build.properties.default Sun Aug 20
17:02:52 2006
@@ -56,18 +56,18 @@
# --
-# - Commons Beanutils, version 1.1 or later -
-commons-beanutils.home=${base.path}/commons-beanutils-1.7.0
+# - Commons Beanutils, version 1.1 to 1.6.1 -
+commons-beanutils.home=${base.path}/commons-beanutils-1.6.1
commons-beanutils.lib=${commons-beanutils.home}
commons-beanutils.jar=${commons-beanutils.lib}/commons-beanutils.jar
-commons-beanutils.loc=${base-jakarta.loc}/commons/beanutils/binaries/commons-beanutils-1.7.0.tar.gz
+commons-beanutils.loc=${base-jakarta.loc}/commons/beanutils/binaries/commons-beanutils-1.6.1.tar.gz
# - Commons Collections, version 1.0 or later -
-commons-collections.home=${base.path}/commons-collections-3.1
+commons-collections.home=${base.path}/commons-collections-3.2
commons-collections.lib=${commons-collections.home}
-commons-collections.jar=${commons-collections.lib}/commons-collections-3.1.jar
-commons-collections.loc=${base-jakarta.loc}/commons/collections/binaries/commons-collections-3.1.tar.gz
+commons-collections.jar=${commons-collections.lib}/commons-collections-3.2.jar
+commons-collections.loc=${base-jakarta.loc}/commons/collections/binaries/commons-collections-3.2.tar.gz
# - Commons Digester, version 1.1.1 or later -
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40252] - Different commons-logging version in web app preventing tomcat startup
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40252. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=40252 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r433099 - /tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/
Author: markt Date: Sun Aug 20 17:24:08 2006 New Revision: 433099 URL: http://svn.apache.org/viewvc?rev=433099view=rev Log: Tag 4.1.33 Added: tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/ - copied from r433098, tomcat/container/branches/tc4.1.x/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r433100 - /tomcat/jasper/tags/tc4.1.x/TOMCAT_4_1_33/
Author: markt Date: Sun Aug 20 17:24:17 2006 New Revision: 433100 URL: http://svn.apache.org/viewvc?rev=433100view=rev Log: Tag 4.1.33 Added: tomcat/jasper/tags/tc4.1.x/TOMCAT_4_1_33/ - copied from r433099, tomcat/jasper/branches/tc4.1.x/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r433101 - /tomcat/servletapi/tags/servlet2.3-jsp1.2-tc4.x/TOMCAT_4_1_33/
Author: markt Date: Sun Aug 20 17:25:43 2006 New Revision: 433101 URL: http://svn.apache.org/viewvc?rev=433101view=rev Log: Tag 4.1.33 Added: tomcat/servletapi/tags/servlet2.3-jsp1.2-tc4.x/TOMCAT_4_1_33/ - copied from r433100, tomcat/servletapi/branches/servlet2.3-jsp1.2-tc4.x/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r433102 - /tomcat/connectors/tags/tc4.1.x/TOMCAT_4_1_33/
Author: markt Date: Sun Aug 20 17:26:49 2006 New Revision: 433102 URL: http://svn.apache.org/viewvc?rev=433102view=rev Log: Tag 4.1.33 Added: tomcat/connectors/tags/tc4.1.x/TOMCAT_4_1_33/ - copied from r433101, tomcat/connectors/trunk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Relation of jasper and servlet API to Tomcat
On Sun, 2006-08-20 at 13:43 -0700, Costin Manolache wrote: If you want to include the real tomcat in gentoo - please use the official label, follow the same procedure as our release, We do include the real Tomcat. Problem is aspects of Tomcat many other apps use. With regard to Jasper I believe it's just Jetty. But servlet-api, a bunch of packages depend on that one. How we version the servlet-api is still up for discussion. Since it's not really based on Tomcat versions. Jasper is another story, and Jasper's package version is likely to stay that of the version of Tomcat it came from. Source wise. and make sure the result of emerge is identical with what the user would get if he would get tomcat from ASF. For the most part were are there, short of one jar, naming-factory-dbcp.jar. However it's possible that Tomcat's on Gentoo could be built with newer versions of dependencies/bundled jars. If you have to patch - and the patch alters the structure or behavior - please don't call the result 'tomcat' :-) We do not modify Tomcat at all. The only patches are to like not download/compile etc jars that are dependencies of Tomcat, or will be bundled. We link those in since they will already exist on the system as a dependency of Tomcat. Beyond that the only thing the patches do is modify/exclude some targets. Since they lack any sort of condition that would allow a command line option for ant to control if those aspects are built. Like examples, docs, etc. We have use flags, if someone does not set examples, docs etc. We do not build/compile that stuff, much less install it. So our patches do not really modify Tomcat at all. Slight modifications to build.xml files only, and to control what get's built when, how, and with what. -- William L. Thomson Jr. Gentoo/Java signature.asc Description: This is a digitally signed message part
svn commit: r433115 - /tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/build.properties.default
Author: markt Date: Sun Aug 20 18:22:16 2006 New Revision: 433115 URL: http://svn.apache.org/viewvc?rev=433115view=rev Log: Set version number Modified: tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/build.properties.default Modified: tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/build.properties.default URL: http://svn.apache.org/viewvc/tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/build.properties.default?rev=433115r1=433114r2=433115view=diff == --- tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/build.properties.default (original) +++ tomcat/container/tags/tc4.1.x/TOMCAT_4_1_33/build.properties.default Sun Aug 20 18:22:16 2006 @@ -28,7 +28,7 @@ #flags.hide=on #Version number -version=4.1 +version=4.1.33 #Proxy to download subproject #proxy.host=proxy.domain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Tomcat 4.1.33 as beta
All, Please vote on releasing Apache Tomcat 4.1.33 as beta. Download from: http://tomcat.apache.org/dev/dist/ MD5s: apache-tomcat-4.1.33-src.tar.gz c4fbeda65a3d7418b129d5ec69fa18de The vote will run for approximately 72 hours. If this VOTE passes, a stability vote will be held a suitable period (at least 2 weeks) after the beta release. For those keeping score, 4.1.32 had a couple of regressions that: - broke the AJP connector - prevented any webapp that shipped commons-logging from loading Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tomcat 4.1.33 as beta
Mark Thomas wrote: All, Please vote on releasing Apache Tomcat 4.1.33 as beta. +1, in case it wasn't obvious ;) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tomcat 4.1.33 as beta
Mark Thomas wrote: All, Please vote on releasing Apache Tomcat 4.1.33 as beta. Download from: http://tomcat.apache.org/dev/dist/ MD5s: apache-tomcat-4.1.33-src.tar.gz c4fbeda65a3d7418b129d5ec69fa18de The vote will run for approximately 72 hours. If this VOTE passes, a stability vote will be held a suitable period (at least 2 weeks) after the beta release. For those keeping score, 4.1.32 had a couple of regressions that: - broke the AJP connector - prevented any webapp that shipped commons-logging from loading +1. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
