Ok, i feel like i'm swimming against the stream. Given the basic requirement of setting up an SSL web service aggregator, what would be the best practice way of using to CXF to set it up? I have XSDs for the services i need to expose (server), and either XSDs or WSDLs for the services i need to consume (as a client). I was trying to get this going with Jetty, but there seems to be little relevant documentation. Should i deploy in, say, Tomcat instead? Would that be more "standard"?

On 3/4/2014 10:58 AM, Matthew Lohbihler wrote:
Hi Willem,

I don't actually get errors, i just don't get configurations loading. But of course the day after complaining about it, it inexplicably starts working. Well, somewhat...

(BTW, i'm using CXF version 3.0.0.)

The ServerFactoryBean is loading my configuration, but now i get errors in the TLS config. I found the following configuration online:

  <httpj:engine-factory bus="cxf">
    <httpj:identifiedTLSServerParameters id="secure">
      <httpj:tlsServerParameters>
        <sec:keyManagers keyPassword="myPassword">
<sec:keyStore type="JKS" password="myPassword" file="conf/.keystore.fc"/>
        </sec:keyManagers>
      </httpj:tlsServerParameters>
    </httpj:identifiedTLSServerParameters>

    <httpj:engine port="9001">
      <httpj:tlsServerParametersRef id="secure" />
      <httpj:threadingParameters minThreads="5" maxThreads="15" />
      <httpj:connector>
        <beans:bean class="org.eclipse.jetty.server.bio.SocketConnector">
          <beans:property name="port" value="9001" />
        </beans:bean>
      </httpj:connector>
      <httpj:handlers>
<beans:bean class="org.eclipse.jetty.server.handler.DefaultHandler"/>
      </httpj:handlers>
<httpj:sessionSupport>true</httpj:sessionSupport>
    </httpj:engine>
  </httpj:engine-factory>

The TLS settings are getting loaded (because errors occur if the keystore file isn't found). But it seems the tlsServerParametersRefisn't getting used, because when i change org.eclipse.jetty.server.bio.SocketConnector to org.eclipse.jetty.server.ssl.SslSelectChannelConnector i get a file not found error on the keystore at a different keystore path (the default path).

How can i get the ssl connector to use the given TLS config?

Thanks,
Matthew


On 3/4/2014 1:36 AM, Willem Jiang wrote:
What kind of error did you get?
Did you put the cxf-rt-http-jetty jar into you class path?


--
Willem Jiang

Red Hat, Inc.
Web:http://www.redhat.com
Blog:http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)  
(English)
http://jnn.iteye.com(http://jnn.javaeye.com/)  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem



On March 4, 2014 at 6:39:45 AM, Matthew Lohbihler ([email protected]) 
wrote:
Hi, I'm trying to set up a CXF instance that acts as a web service
aggregator over https. The examples that i've seen that use Jetty
either
start the server using a ServerFactoryBean or a
ClassPathXmlApplicationContext, but these don't seem to work
for me.
I've created a cxf.xml file in which i can configure the service
and the
https endpoint, but i can't seem to figure out how to properly
start CXF
so that the configuration file gets loaded. What am i missing?
Many thanks,
Matthew



Reply via email to