Yes the wrong saving SSL Connector is a bug and I fix it for Tomcat 5.5.x.
The old StandardServer saving code was strange. The new StoreConfig module has
a flexible customizable API to store server.xml and context.xml.
You can activate the new saving module with
<Server ...>
<Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
.... </Server>
This listener register a new MBean with more options to save the tomcat configurations.
Give 5.5.9 a try ... :-)
Peter
Jeffrey Barnett schrieb:
Mike, unfortunately I'm only gotten better at restoring server.xml after it has been corrupted. You are the first person from the tomcat-user list to even confirm that the problem exits on other sites.. One consultant I consulted said that they had never heard of the problem, but that we were also the first site he had worked with that actually used the admin function actively, By the way, just for the record, not only the secure attribute, but also the protocol attribute is duplicated, right? And only on the SSL connector.
Mike Dippold wrote:
I just wanted to check to see if you have figured anything out with the tomcat admin ssl duplicate problem. I have tried it on 5.0.28 and also 5.5.7 and every time I change a datasource or anything else, it corrupts the xml.
Thanks,
Mike Dippold
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
