I looked in the apache bug database and found bug #29096 that refers to this problem. It is in the "RESOLVED-INVALID" state however, and claims that windows services are not supposed to allow dashes in their names.
Well, the procrun uses the IsCharAlphaNumeric function to determine the validity of service name, so [A-Z][0-9].
I don't think that's correct, and have found some references on the web that state otherwise. Dashes were allowed under tomcat-5.0.16, but now they are not under tomcat-5.0.27. Windows (2003) allows it, but for some reason tomcat no longer does.
Sure It's not, the dashes are allowed (perhaps). You may reopen the bug with 'enhancement', since it's only a cosmetic. Further more you can create a patch, that will allow all the possible non-alnum characters, together with the proof that they are working on NT4...WIN2K3. I'm almost sure that NT4 does not allow spaces in service name.
So, since 90% of services (quick browse trough my registry) are using only alnum chars, I'm -0 on that subject, cause don't think it's worth
of effort. What would be worth is testing whether IsCharAlphaNumeric itself has a potential characters (they are locale based) that may
break the functionality.
Regards, MT.
smime.p7s
Description: S/MIME Cryptographic Signature
