I have attached the wsdl and schema files (except for STAKE.xsd, it was too
large). Hopefully the wsdl is all you need. If not, I can send it to you
STAKE.xsd separately.
My consumer service and provider service use the same wsdl. The whole
operation is just a pass-thru. The provider adds WS-Security headers, but
other than that everything is the same. Here it is:
<cxfbc:provider wsdl="classpath:wsdl/DataGateway.wsdl"
locationURI="http://outsideserver:8081/gateway/services/DataMaintenanceService";
endpoint="DataMaintenanceSOAPPort"
service="dgw:DataMaintenanceService">
<cxfbc:inInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingInInterceptor"/>
</cxfbc:inInterceptors>
<cxfbc:outInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingOutInterceptor"/>
<ref bean="saajout"/>
<ref bean="TimestampSignEncrypt_Response"/>
<bean class="com.issinc.apache.cxf.ContentTypeFixer"/>
</cxfbc:outInterceptors>
<cxfbc:inFaultInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingInInterceptor"/>
</cxfbc:inFaultInterceptors>
<cxfbc:outFaultInterceptors>
<bean class="org.apache.cxf.interceptor.LoggingOutInterceptor"/>
</cxfbc:outFaultInterceptors>
</cxfbc:provider>
<bean
class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor"
id="TimestampSignEncrypt_Request">
<constructor-arg>
<map>
<entry key="action" value="UsernameToken"/>
<entry key="passwordCallbackClass"
value="org.apache.servicemix.samples.cxf_ws_security.KeystorePasswordCallback"/>
</map>
</constructor-arg>
</bean>
--
View this message in context:
http://www.nabble.com/SOAPFault-not-returning-in-CXFBC-Consumer-tp18716659p18755203.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
