Enhancing HTTP-based connector to support SSL

Hi all,

I am enhancing the HTTP-based connectors to support SSL in a simpler
way.

Right now it is possible to start an external web container and tell
MX4J to use that instead of starting a new one. This is the only way to
use SSL.

What I'd like to do is to support JMXServiceURLs like these ones:

service:jmx:hessian+ssl://localhost/hessian

This way, connector servers can be started in SSL mode with little
support.
One thing that is not, IMHO, movable into MX4J is the web container
configuration.
Right now MX4J support a simple configuration out of the box, that
simply adds a listener on the JMXServiceURL port.
However, it is not recommendable to mimic the web container (specific)
API to support listener configuration such as:
+ max/min threads
+ connection timeouts
+ confidential redirect port
+ SSL configuration parameters
+ etc.

So the idea is that, to fine tune the web container, one passes a
configuration file, that most  web containers can read to self
configure.
This is possible passing the property
MX4JRemoteConstants.HTTP_SERVER_CONFIGURATION in the environment Map.

So, it will be sufficient to pass to MX4J a simple web container
configuration file with only listeners configured, and MX4J will do the
rest (deploy servlets, mapping them to JMXServiceURLs and starting the
web container).

I have already done this:
+ Refactoring of the ConnectionResolver to support protocols with "+".
+ Refactoring of class names for soap, hessian and burlap.
+ Modifications needed to remove hardcoded "http" strings

With these small refactorings, I have hessian+ssl working fine.

Comments welcome.

Simon
-- 
http://bordet.blogspot.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click