mvn clean install of the reproducer.zip Then on a standalone Fuse 6.3 R16: fabric:create --clean -g localip -r localip --wait-for-provisioning profile-import mvn:org.acme.demo/acme-demo-cxf-discovery-provider-profile/1.0.0-SNAPSHOT/zip/profile profile-import mvn:org.acme.demo/acme-demo-cxf-discovery-consumer-profile/1.0.0-SNAPSHOT/zip/profile container-create-child --profile acmetz-demo-cxf-discovery-provider-profile root acmetz-cxf-provider container-create-child --profile acmetz-demo-cxf-discovery-consumer-profile root acmetz-cxf-consumer Now there is a rest web service that consume the two load balanced webservices. If you call the consumer rs with: curl -v -X GET -i -H "Accept: application/json"  [http://[consumer|http://[consumer/] node]:8183/cxf/consumerrs/rs to consumer the jax-rs or the curl -v -X GET -i -H "Accept: application/json" [http://[consumer|http://[consumer/] node]:8183/cxf/consumerrs/ws to consume the jax-ws the response will be always 404. Look in ZK with zk:get /fabric/cxf/endpoints/providerrs/00000000000 you will find "services":["[http://[producer|http://[producer/] node]/providerrs"]} instead _ "services":["[http://[producer|http://[producer/] node]/cxf/providerrs"]}_ Modify the zk node with zk:edit /fabric/cxf/endpoints/providerws/00000000000 adding the missing /cxf and now the consumer ws that use jax-rs is able to reach the provider was (the same for jax-ws ws)