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 Tue, 22 May 2007 03:36:16 GMT


Steven E. Harris commented on CXF-628:

Here's one function, with the application-specific names changed to protect the innocent:

   private static MyInterface_Service makeConfiguredService() {
      final MyInterface_Service service =
            new MyInterface_Service( null,
                                             new javax.xml.namespace.QName( nsMyInterface,
) );
      service.addPort( new javax.xml.namespace.QName( nsMyInterface, "my-interface-soap-endpoint"
                       "http://localhost:8888/some/context/path/ws/my-interface" );
      return service;

Given some WSDL with a service named "my-interface" with a port named "my-interface-soap-endpoint",
we want to indicate that this port is bound to SOAP 1.2 over HTTP, equivalent to WSDL elements
like the following:

  <binding name="my-interface-soap" type="tns:my-interface">
    <wsoap12:binding transport=""/>


  <binding name="my-interface-soap" type="tns:my-interface">
    <wsoap12:binding transport=""/>

I could also show the similar WSDL 2.0 if that would be helpful.

> 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