cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven E. Harris (JIRA)" <>
Subject [jira] Commented: (CXF-628) Service.addPort(QName, String, String) does not accept binding ID
Date Thu, 24 May 2007 19:32:16 GMT


Steven E. Harris commented on CXF-628:

All is well today. I'm able to use Service.addPort() and get SOAP 1.2 over HTTP as expected.
Now I need to ping someone (Dan?) who was going to look into why the SOAP action parameter
is a header all its own rather than a parameter to the Content-Type header.

Actually, wait: I just noticed my messages are being produced with two Content-Type headers:

POST /host/my-interface HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8
action: "http://host/my-interface-service/some-operationRequest"
Content-Type: text/xml
Connection: close
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.6.0_01
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-Length: 469

I'll file a second issue about this.

> 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