[jira] Created: (CXF-669) When SEI's and IMPLS have different namespaces, we don't generate the correct WSDL(s)

[Daniel Kulp (JIRA)]

When SEI's and IMPLS have different namespaces, we don't generate the correct 
WSDL(s)
-------------------------------------------------------------------------------------

                 Key: CXF-669
                 URL: https://issues.apache.org/jira/browse/CXF-669
             Project: CXF
          Issue Type: Bug
          Components: Tooling
    Affects Versions: 2.0-RC
            Reporter: Daniel Kulp
         Assigned To: maomaode
             Fix For: 2.0



If the IMPL's WebService annotation specifies a different targetNamespace than 
the SEI interface, we don't generate a valid wsdl.   We need to generate two 
wsdls, one for the SEI interface and another for the service (which then 
imports the one for the SEI).



package com.foo;

import javax.jws.WebParam;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding.Style;
import javax.jws.soap.SOAPBinding;
import javax.jws.WebMethod;
import javax.jws.WebResult;

@WebService(targetNamespace = "http://foo.com/HelloWorld";, name = "HelloWorld")
@SOAPBinding(style = SOAPBinding.Style.RPC)
public interface Hello {

    @WebResult(partName = "out", name = "out")
    @WebMethod
    public String echoFoo(
                @WebParam(partName = "in", name = "in")
                String s);
}




package com.foo;

import javax.jws.WebService;

@WebService(serviceName = "HelloService", 
            portName = "HelloPort", 
            endpointInterface = "com.foo.Hello",
            targetNamespace = "http://foo.com/HelloWorldService";)
public class HelloImpl {

    public String echoFoo(String s) {
        return s;
    }

}


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