Support simultaneous http and https connectors in tomcat5x

Would be a great feature in my selfish opinion if tomcat5x supported both http and https connectors simultaneously. At time of writing, all cargo versions out-of-the-box allow one connector or the other, not both. Ideally the maven2 cargo plugin would support this feature to.

--------------------------------
Taken from mailing list:

Hi all,

I'm using the cargo maven2 plugin to run the tomcat5x container. The
build then runs a few functional tests against this requesting both
SSL and non-SSL URLs.

What I'm working on now is having a single standalone self-installing
tomcat5x container with both http and https protocols supported.
Out-of-the-box tomcat5x cargo currently only supports one protocol or
the other, not both at the same time.

As proof of concept, both http and https can be supported at once by
adding the following connector element to the tomcat5x server.xml file
in the cargo-core-container-tomcat-0.8.jar jar in the local maven
repository:

<Connector port="443"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"
scheme="https" secure="true"
debug="2"/>

This works because the generated server.xml specifies two connectors
(one for http, one for SSL / https) instead of the single connector.

I'd rather fix this in a cleaner way, so is there a recommended way to do this?

Many thanks in advance,

Eliot

P.S. For SSL support you will also need to generate a .keystore file
in your user.home directory with the following commands:
$> cd
$> keytool -keystore .keystore -genkey -alias anything -keyalg RSA
When prompted for passwords by the keytool, always use 'changeit' as
this is the default password expected by tomcat.

------------------------
In response, Matt Wringe wrote:

currently, no, this is the only 'fix' for now. The next version should
include support for specifying external xml configuration files, so
instead of having to change the file inside the jar you can just have
cargo use a file on your file system.

I do agree that setting up both http and https should be something that
cargo handles itself and shouldn't need any changes to support it.

Could you please open a bug report requesting support for simultaneous
http and https connectors?