Thanks, Charles and Bill. This has been most helpful. I will be looking and both alternatives.
mike -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Saturday, October 15, 2005 5:56 PM To: tomcat-user@jakarta.apache.org Subject: Re: Hijacking the coyote connector There should never be a reason to replace the Connector in Tomcat, since all it does is serve as a bridge. Also, in TC 5.5.x, the Connector is strongly integrated with the container code, so it is is almost certainly more trouble than it is worth to try. The recommended way to do what it sounds like you want is implement your own ProtocolHandler (http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/co yote/ProtocolHandler.html). You tell Tomcat to use your ProtocolHandler by: <Connector protocol="com.unisys.mypackage.MyProtocolHandler" ... /> Any other xml attributes you put in the <Connector> tag will be passed to your class in JavaBean convention. You will also likely want to define an ActionHook (http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/co yote/ActionHook.html) to get Tomcat to work properly with your implementation. "Dobbins, Michael G" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] om... In tomcat 5.0.28, we were able to replace the coyote connector using a "className" setting in the connector in server.xml. In tomcat 5.5.9 it looks like "className" is ignored. Looking at the source, it looks like the Connector is hardcoded in. Is this the case or am I missing something? My next attempt, I repackaged our connector to replace the org.apache.catalina.connector package and put that in the -Xbootclasspath to override the released version. With -verbose:class set I can see my Connector being loaded, but the next class loaded is java/lang/reflect/InvocationTargetException and the JVM terminates. The documentation says that this is used to wrap an exception when a method or constructor is called by reflection. As I said above it looks to me like the constructor is called directly not via reflection. Am I missing something obvious? I know that using the AJP connector is a cleaner way, but we estimate the serialization overhead will cost us about 5% on our platform. Thanks mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
