Hi.

Recently, other people and myself were looking for a pre-packaged mod_jk binary for a RedHat RHELS system.

As a result of some investigation (by Mark Eggers on one side, and an independent sysadmin of my customer on the other side), things seem to boil down to (largely quoted) :

"
In the RedHat product "Red Hat Enterprise Linux Server" (RHELS), there is no repository containing a pre-packaged mod_jk module.

To obtain such a package, the client has to purchase the separate RedHat package "JBoss Enterprise Web Server", which contains mod_jk.
"

I would suppose that RedHat has good lawyers, and that they are "allowed" to do such a thing. Personally, I find this a bit "cheeky", specially from a company that presents itself as a champion of Open Source. It is not an unmitigated feeling, because on the other hand I also recognise that mod_jk is a complex piece of software, and that supporting it for customers certainly has a cost.

But whatever the real merits of my personal feelings in the matter,
there are people (even sysadmins) who are comfortable with the idea of installing a software package from sources; but there are also many people who simply do not have the time to go through the hassle, and people who are uncomfortable with the installation of such packages (because of maintenance reasons, patches etc.), and people who are just not allowed to install anything that is not part of the standard corporate repository.

In the practice thus, it probably means that a number of people will no longer use mod_jk on RHEL systems in the future, and I find this a pity, because even from a purely technical point of view, it is always better to have some alternatives. And there are things which you can do with mod_jk, which you cannot with mod_proxy_ajp and/or mod_proxy_http (and probably vice-versa).

Anyway, I wonder if anyone here has another opinion on the matter.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to