cxf-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/CXF-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498788
] 

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
Host: 127.0.0.1:8888
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 javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-628
>                 URL: https://issues.apache.org/jira/browse/CXF-628
>             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 javax.xml.ws.Service.addPort() method, as described here:
> http://java.sun.com/javase/6/docs/api/javax/xml/ws/Service.html#addPort(javax.xml.namespace.QName,%20java.lang.String,%20java.lang.String)

> Per the documentation, one should specify the constant 
>   javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING
> 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 http://www.w3.org/2003/05/soap/bindings/HTTP/
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createBindingInfo(AbstractEndpointFactory.java:255)
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createEndpointInfo(AbstractEndpointFactory.java:182)
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(AbstractEndpointFactory.java:104)
> 	at org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:44)
> 	at org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:82)
> 	at org.apache.cxf.jaxws.ServiceImpl.createPort(ServiceImpl.java:314)
> 	at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:237)
> 	... 9 more
> Caused by: org.apache.cxf.BusException: No binding factory for namespace http://www.w3.org/2003/05/soap/bindings/HTTP/
registered.
> 	at org.apache.cxf.binding.BindingFactoryManagerImpl.getBindingFactory(BindingFactoryManagerImpl.java:78)
> 	at org.apache.cxf.frontend.AbstractEndpointFactory.createBindingInfo(AbstractEndpointFactory.java:250)
> 	... 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.


Mime
View raw message