[CXF-6866] bindingId on Client/ServerFactoryBean does not overrule WSDL

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.6, 3.0.9
• Fix Version/s: 3.0.13, 3.1.11, 3.2.0
• Component/s: Core
• Labels: regression
• Estimated Complexity: Unknown
• Assignee: Freeman Fang
• Reporter: Jens Kleine-Herzbruch
• Created: 13/Apr/16 06:51
• Updated: 10/Apr/17 19:04
• Resolved: 16/Feb/17 06:05

Description

I have a regular service WSDL with a SOAP/HTTP binding.

I want to use the XML binding with the service, though. If I set up my service like this:

        ServiceImpl implementor = new ServiceImpl();
        JaxWsServerFactoryBean svrFactory = new JaxWsServerFactoryBean();
        svrFactory.setServiceClass(ServiceInterface.class);
        svrFactory.setAddress(HTTP_ADDRESS);
        svrFactory.setServiceBean(implementor);
        svrFactory.setBindingId("http://cxf.apache.org/bindings/xformat");

everything works as expected. However, if I also add these three lines

        svrFactory.setWsdlURL(wsdlUrl);
        svrFactory.setServiceName(new QName(SERVICE_NS, SERVICE_NAME));
        svrFactory.setEndpointName(new QName(SERVICE_NS, PORT_NAME));

the the port definition from the WSDL takes precedence over the factory configuration, and the service expects a SOAP request. Other properties, like e.g. the transportId, get overridden just fine.

The same problem also seems to exist on the ClientFactoryBean side.

This used to work in CXF 2.x.