RE: Enhancing HTTP-based connector to support SSL

Superbonbon, 

> > The solution i have concerning the webcontainer config 
> > "issue" is to 
> > build via a
> > simple custom API a complete config file for jetty with one 
> > http or https
> > listener. Save the xml file on hard disk and then instruct 
> > mx4j with the
> > MX4JRemoteConstants.HTTP_SERVER_CONFIGURATION env param to use the
> > freshly built config file.
> 
> Uhm. What about a simpler solution: ship with MX4J an example 
> that shows
> how to create an http/https-based connector with a sample Jetty
> configuration file ?

Example and documentation added.

> It is however true that a simple Jetty configuration file can 
> be shipped with MX4J...
> I see your point, will think some more about it.

Well, the main purpose of shipping a default configuration was to avoid
the user to add objects to the environment map, so that the connectors
will work out of the box.
I've tried to implement this, but ended up with a problem: the
certificate that needs to be stored in the keystore depends on the host
the server is running on (in particular the common name must match).
So finally the keystore must be created externally and passed in anyway
(even if I can get rid of the web container configuration file). At this
point I prefer to leave the whole configuration external.

Unless someone has a definitive solution, I'll stick with this one for
MX4J 3.0, there always is time to improve in a future release.

Simon


-------------------------------------------------------
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