Adding this mail to webstack-discuss so that it gets archived

Date: Wed, 21 Nov 2007 10:48:38 +0100
From: Rainer Jung
Subject: Re: mod_jk compatibilities between versions.
To: Tomcat Users List <users at tomcat.apache.org>

rahul wrote:
>| >     I am trying to integrate mod_jk with the apache 2.2 package
>| > distribution in solaris.
>| > I would like to know what would be the versions that can have
>| > incompatibilities with the previous versions (both API and 
>configuration)
>
>| Check the change log:
>| http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html
>
>thanks I will check it.
>
>| It contains all changes between each version. If you need to know what
>| changed between 1.2.14 and 1.2.25, then you need read all of the changes
>| for intervening versions.
>| 
>| > Is JK-1.2.25 going to be completely compatible with JK-1.2.26
>| 
>| All of the 1.2.x versions are compatible with each other.
>| 
>| > How about JK-1.2.25 and JK-1.3.xx and 
>| 
>| I don't believe there are any 1.3.x versions.
>
>I had meant it for the future versions. ie. at what version level change
>can I expect the compatibility to get broken (If there is a reason for
>breaking it). To ask in a different way, If you find that you need to
>break the compatibility between releases, which version number will you
>increment?.

Any version in the 1.2.x line will be compatible in the sense, that 
configs working for older versions will work at least as well for newer 
versions. There have been very few exceptions, e.g. we sometime 
introduced a new feature in some 1.2.x release and immediately observed 
a problem with it's semantics, so we needed to change it in 1.2.(x+1). 
Another example was, when we started to enhance the status worker a lot, 
we broke the URL structure (query argument names). But we really try 
hard to stay compatible in the 1.2.x line. If a feature is completely 
new in 1.2.x, there is some risk, that we need to make a change to it 
soon after the first release of it. We don't expect a lot of new 
features for the existing mod_jk, it's pretty stable now.

The only other existing major jk version is mod_jk2, which is 
incompatible from a configuration point of view and deprecated. Although 
that project started later then mod_jk, it is no more alive and all 
important features of mod_jk2 have been backported to mod_jk.

We have a plan to start a JK3. This again will be incompatible with 
mod_jk and mod_jk2, but work didn't really start until now, so a first 
release is still far away.

There is no mod_jk 1.3 or similar, and there are no plans for it.
This message posted from opensolaris.org


Reply via email to