Wo, hang on there Remy. I'm sorry, I really didn't mean to cause offence.
Point 1, Ok, fair enough, I'm a twat. But I did ask the question! When is mod_jk2 going to replace mod_jk anyway?
I don't know. It is not critical IMO, as mod_jk works fine.
On point 2. I downloaded the zip. I have just downloaded the exe to see what shortcuts you are talking about and Ok, a nice screen to configure the service. I did read the documentation. I also had to look in a readme file in cvs Jakarta-commons/daemon to find out how procrun is run (which doesn't even mention the //ES// parameter), but if you're telling me that adding a service in the set up I described is user friendly then I have to disagree. That's not to say, I don't think it's heading in the right direction, because I think it is. But it took 5 minutes to get TC5 up and running with jk_nt_service and about 2 hours to sort it out with procrun.
If you want the "do-it-yourself" experience, then use the .zip. Setting up Tomcat with the service is meant to be done through the installer, so the user experience is decent.
Besides, the wrapper tool is external to Tomcat. If you want to use the old JavaService or jk_nt_service, then you can.
And I think maybe I worded it a bit harshly. We will be moving onto TC5 as soon as its final (which we didn't do for TC4.0!).
I was going to look at writing some code tonight so that the Apache HTTP Service Monitor picks up and controls TC5 services and also look at how procrun (because it is mainly there) can be improved.
Personally, I like the current syntax. Unlike you, I think it is complete, and rather intuitive. -1 to change it.
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
