Hi,
Could you append your jetty.xml?
Is it possible that your customized defaultHandler modify the
requestContext path so that the incoming request is not
http://0.0.0.0:8193/services/circuit?wsdl ?
Freeman
Jack Jack wrote:
Hi
I am using servicemix 3.2.2 and trying to set the custom jetty server for CXF-BC consumer.
I defined the consumer in light-weight mode in the servicemix.xml as as below.
<sm:component>
<cxfbc:component>
<cxfbc:endpoints>
<cxfbc:consumer wsdl="/WEB-INF/wsdl/CircuitIR.wsdl"
busCfg="jetty.xml"
service="ckt:FrameRelayCircuit"
interfaceName="ckt:FrameRelayCircuitPortType"
targetEndpoint="CircuitPort"
targetService="ckt:FrameRelayCircuit"
targetInterface="ckt:FrameRelayCircuitPortType" />
</cxfbc:endpoints>
</cxfbc:component>
</sm:component>
And in cxf.xml file, defined the Jetty-factory and jetty engine with the port
8193. And the same port numebr was specified in the WSDL file also for service
address.
Additinally I defined the handlers DefaultHandler,WebAppContext handler in the cxf.xml.
Jetty engine and handles were sepecified as per http://cxf.apache.org/schemas/configuration/http-jetty.xsd
Upon server start up no errors were thrown, but
1) The web service is not responding. Tried to access WSDL using the URL the
http://localhost:8193/services/circuit?wsdl
The console logs are shown as below.But failed to retrieve the WSDL.
INFO: Setting the server's publish address to be http://0.0.0.0:8193/services/circuit
...
INFO: Started [email protected]:8193
I tried the address in the WSDL file with localhost instead of 0.0.0.0 but the result is same.
2) The org.mortbay.jetty.webapp.WebAppContext handler that I defined in cxf.xml is working fine.
Able to access the html pages using the link for example
http://0.0.0.0:8193/test/circuit.html
The problem is I need to use the same jetty server/engine running on 8193 for both CXF-BC consumer and webAppContext handler.
I appreciate your help on resolving this issue.
Thanks
Jack
