William A. Rowe, Jr. wrote:
Mladen Turk wrote:
It's irrelevant.
5.5.16 will not work with 1.1.1
jknative is getting there, for sure :) But is it there yet?
I should have asked the question this way instead...
"Is jknative a faster moving target than the Tomcat 5.5 releases themselves?"
-
Mladen Turk wrote:
It's irrelevant.
5.5.16 will not work with 1.1.1
Then I'd think there are two solutions;
1. repackage 5.5.16 -without- jknative.
2. roll 5.5.17 with jknative 1.1.2
It sounds like the 5.5.16 package is fundementally flawed. Retracting
a component to avoid confusion amoung
William A. Rowe, Jr. wrote:
Fenlason, Josh wrote:
I should have checked this before the vote for 5.5.16 was closed, but I
just realized that in 5.5.16 the native connector is still at 1.1.1.
Question, does TC-Native 1.1.1 share the same flaw as mod_jk,
mod_proxy_ajp?
It's irrelevant.
5.5
Fenlason, Josh wrote:
I should have checked this before the vote for 5.5.16 was closed, but I
just realized that in 5.5.16 the native connector is still at 1.1.1.
Question, does TC-Native 1.1.1 share the same flaw as mod_jk, mod_proxy_ajp?
We would need to repack the 5.5.16 or release 5.5.17
Fenlason, Josh wrote:
I should have checked this before the vote for 5.5.16 was closed, but I
just realized that in 5.5.16 the native connector is still at 1.1.1.
Me too :(
That's bad.
Does the Tomcat native connector have it's own release cycle?
Yes.
We would need to repack the 5.5.16 or r
