Configuring SSL

To configure the standalone HTTP transport to use SSL, you'll need to add an <http:destination> definition to your XML configuration file. See the Configuration guide to learn how to supply your own XML configuration file to CXF. If you are already using Spring, this can be added to your existing beans definitions. For more information about configuring TLS, see the Configuring TLS page.

Destinations in CXF are responsible for listening for server side requests.

<beans xmlns=""

  <http:destination name="{}GreeterImplPort.http-destination">    
  <httpj:engine-factory bus="cxf">
  <!-- you just need to specify the TLS Server configuration for the certain port -->
    <httpj:engine port="9003">
        <sec:keyManagers keyPassword="password">
          <sec:keyStore type="JKS" password="password" 
          <sec:keyStore type="JKS" password="password"
          <!-- these filters ensure that a ciphersuite with
               export-suitable or null encryption is used,
               but exclude anonymous Diffie-Hellman key change as
               this is vulnerable to man-in-the-middle attacks -->
        <sec:clientAuthentication want="true" required="true"/>

Add the static content pages into the jetty server

The CXF standalone http transport is based on the jetty server. The code below shows how to get the jetty server from the destination and how to add the static content path to the jetty server.

    // get the jetty server form the destination
    EndpointInfo ei = new EndpointInfo();
    Destination destination = df.getDestination(ei);
    JettyHTTPDestination jettyDestination = (JettyHTTPDestination) destination;
    ServerEngine engine = jettyDestination.getEngine();
    Handler handler = engine.getServant(new URL(serviceFactory.getAddress()));
    org.mortbay.jetty.Server server = handler.getServer(); // The Server

    // We have to create a HandlerList structure that includes both a ResourceHandler for the static
    // content as well as the ContextHandlerCollection created by CXF (which we retrieve as serverHandler). 
    Handler serverHandler = server.getHandler();
    HandlerList handlerList = new HandlerList();
    ResourceHandler resourceHandler = new ResourceHandler();

    // replace the CXF servlet connect collection with the list.
    // and tell the handler list that it is alive.

    // setup the resource handler
    File staticContentFile = new File(staticContentPath); // ordinary pathname.
    URL targetURL = new URL("file://" + staticContentFile.getCanonicalPath());
    FileResource fileResource = new FileResource(targetURL);

Configuring Standalone Jetty in OSGi

An OSGi application can use the standalone transport by incorporating cxf-rt-transports-http-jetty, which is an OSGi bundle, and creating
services with endpoint URLs like

If your application needs to configure Jetty, is has to communicate with CXF's mechanism for this purpose, which lives in

CXF allows an application to use different configuration parameters for different 'engines'. An engine is
specified by three properties:

  • HTTP vs. HTTPS (protocol)
  • host
  • port

For each endpoint, CXF allows you to specify:

  • sessionSupport
  • continuationsEnabled
  • reuseAddress
  • maxIdleTime
  • a giant, complex, raft of TLS parameters for HTTPS.

Each of these engines is a shared resource, in that many endpoints can coexist on an engine. Thus, these shared
parameters can't be configured as part of launching an endpoint.

Instead, CXF (in HTTPJettyTransportActivator), creates an OSGi ManagedServiceFactory. Usually, a managed service
factory is a creature that creates multiple OSGi services on demand, each with a particular configuration.
CXF doesn't really do that. Instead, each time that an application publishes a configuration, CXF sets the parameters
for the engine described by the configuration properties.

Concretely, if an application calls the createFactoryConfiguration method of the `ConfigurationAdmin` service for PID
`org.apache.cxf.http.jetty`, CXF looks in the properties. It expects to find `host` and `port`. If it finds
any TLS parameters, it configures for HTTPS. If not, it configures for HTTP. It then applies all the other parameters
to the engine for that [protocol,host,port] triple.

If your application needs to create such a configuration and then modify if (all before CXF actually starts up the engine), you must use code like:

parsed[0], ConfigurationFileReaderImpl.INSTANCE_ID, parsed[1]));


to locate the configuration you created before, where "ConfigurationFileReaderImpl.INSTANCE_ID" is just an example of how you would use a property of your own choice to uniquely specify the configuration.



  • No labels