Has anyone shown any interest in developing a Tomcat 4.0 connector for IIS?
If not this is actually something that I'd like to work on. Unfortuntely,
it is going to be a month or more before I could devote a lot of time to it.
> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 15, 2001 2:00 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FW: Jakarta PMC Meeting Agenda / Info
>
>
> GOMEZ Henri wrote:
>
> > [finally ... a technical issue!]
> > I still didn't understand why TC 4.0 didn't select mod_jk as
> > their connector to WebServer. The code is clean and many bugs
> > are removed. A web server connector is not an easy piece of cake
> > so why reinvent the whell ?-(
> >
>
> Tomcat 4.0 did not select mod_jk for several reasons. The most
> important ones
> are at the top:
>
> * MOD_JK (like MOD_JSERV before it) has no clue what a web
> application is. This forces you to configure many items twice --
> once in the web.xml file and once in the Apache configuration,
> which is a pretty serious imposition on people trying to administer
> the combination.
>
> * While the 2.2 spec was silent in many areas, the 2.3 spec will
> require an Apache+Tomcat combination to obey *all* the requirements
> of the spec (same rules as for any other container). This means that
> the things in web.xml *must* be respected. For example, a security
> constraint in a web.xml file must be enforced, even on a static resource
> that is served by Apache instead of Tomcat. Substantial modifications
> to MOD_JK would be needed to make this work (primarily in adding a
> two-way exchange of configuration information).
>
> * MOD_JK had no committers interested in maintaining it, at the time
> that the decision was made. Subsequent to that time, several
> volunteers have surfaced, including at least one person interested in
> supporting MOD_JK under Tomcat 4.0. That would be fine with me,
> as long as the result obeys all the rules.
>
> Craig McClanahan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
