cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <>
Subject [jira] Commented: (CXF-628) Service.addPort(QName, String, String) does not accept binding ID
Date Wed, 23 May 2007 02:19:16 GMT


Freeman Fang commented on CXF-628:

If you still see this problem today, give me a shout
btw, my test code on client side is 
public void testAddPortWithSpecifiedBinding() throws Exception {
        QName fakePortName = new QName("",
        Service service = Service.create(serviceName);
        Greeter greeter = service.getPort(fakePortName, Greeter.class);

        String response = new String("Bonjour");
        try {
            String reply = greeter.sayHi();
            assertNotNull("no response received from service", reply);
            assertEquals(response, reply);
        } catch (UndeclaredThrowableException ex) {
            throw (Exception)ex.getCause();
On server side is 
//publish port with soap12 binding
        address = "http://localhost:9009/SoapContext/SoapPort";
        EndpointImpl e = (EndpointImpl) Endpoint.create(,

And the wsdl in test is wtih saop11 binding, I believe it's same as your scenario. 

And the messasge I catch is
<soap:Envelope xmlns:soap=""><soap:Body><sayHi
xmlns:ns2="" xmlns=""

It should use soap12 binding now

> Service.addPort(QName, String, String) does not accept binding ID
> ------------------------------------------------------------------------------------------------------------------
>                 Key: CXF-628
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.0-RC
>         Environment: NA
>            Reporter: Steven E. Harris
>         Assigned To: Freeman Fang
>            Priority: Minor
>             Fix For: 2.0
> I'm trying to using the method, as described here:

> Per the documentation, one should specify the constant 
> for the bindingId parameter to request a SOAP1.2-over-HTTP binding. When I try to use
this constant in CXF, I see the following exception:
> [...]
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Could not resolve
a binding for
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createBindingInfo(
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createEndpointInfo(
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(
> 	at org.apache.cxf.frontend.ClientFactoryBean.create(
> 	at org.apache.cxf.frontend.ClientProxyFactoryBean.create(
> 	at org.apache.cxf.jaxws.ServiceImpl.createPort(
> 	at org.apache.cxf.jaxws.ServiceImpl.getPort(
> 	... 9 more
> Caused by: org.apache.cxf.BusException: No binding factory for namespace
> 	at org.apache.cxf.binding.BindingFactoryManagerImpl.getBindingFactory(
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createBindingInfo(
> 	... 15 more
> I can see that the file "META-INF/cxf/cxf-extension-soap.xml" is getting loaded by the
Bus, which I thought would enable SOAP 1.2 for use.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message