[jbossws-issues] [JBoss JIRA] (JBWS-3534) JBossWS CXF ignoring wsdlLocation attribute in @WebService annotation

[emollient mind (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

emollient mind updated JBWS-3534:
---------------------------------

    Description: 
when wsdlLocation attribute is specified on the @WebService annotation the service fails to deploy. log shows wsdlLocation=null.

source of Bug 

class Name :  org.jboss.wsf.stack.cxf.metadata.MetadataBuilder

Method name : protected DDEndpoint createDDEndpoint(Class<?> sepClass,  
                        ArchiveDeployment dep, Endpoint ep)


code :

 // the attribute wsdlLocation is ignored at the time of annotation   
    processing of @WebService

 DDEndpoint result = new DDEndpoint();
      
      result.setId(ep.getShortName());
      result.setAddress(ep.getAddress());
      result.setImplementor(ep.getTargetBeanName());
      result.setMtomEnabled(isMtomEnabled(ep.getTargetBeanClass()));
      result.setEpClass(seiClass != null ? seiClass : sepClass);
      result.setPortName(new QName(serviceNS, portName));
      result.setServiceName(new QName(serviceNS, serviceName));
      Map<String, Object> props = new HashMap<String, Object>();
      for (String k : ep.getProperties()) {
         props.put(k, ep.getProperty(k));
      }





  was:
when wsdlLocation attribute is specified on the @WebService annotation the service fails to deploy. log shows wsdlLocation=null.

source of Bug 

class Name :  org.jboss.wsf.stack.cxf.metadata.MetadataBuilder

Method name : protected DDEndpoint createDDEndpoint(Class<?> sepClass,  
                        ArchiveDeployment dep, Endpoint ep)


code :

 DDEndpoint result = new DDEndpoint();
      
      result.setId(ep.getShortName());
      result.setAddress(ep.getAddress());
      result.setImplementor(ep.getTargetBeanName());
      result.setMtomEnabled(isMtomEnabled(ep.getTargetBeanClass()));
      result.setEpClass(seiClass != null ? seiClass : sepClass);
      result.setPortName(new QName(serviceNS, portName));
      result.setServiceName(new QName(serviceNS, serviceName));
      Map<String, Object> props = new HashMap<String, Object>();
      for (String k : ep.getProperties()) {
         props.put(k, ep.getProperty(k));
      }

Bug fix : add missing statement :  result.setWsdlLocation(...)




    
> JBossWS CXF ignoring wsdlLocation attribute in @WebService annotation
> ---------------------------------------------------------------------
>
>                 Key: JBWS-3534
>                 URL: https://issues.jboss.org/browse/JBWS-3534
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-4.0.2
>         Environment: All, JBoss AS 7.1
>            Reporter: emollient mind
>            Priority: Critical
>
> when wsdlLocation attribute is specified on the @WebService annotation the service fails to deploy. log shows wsdlLocation=null.
> source of Bug 
> class Name :  org.jboss.wsf.stack.cxf.metadata.MetadataBuilder
> Method name : protected DDEndpoint createDDEndpoint(Class<?> sepClass,  
>                         ArchiveDeployment dep, Endpoint ep)
> code :
>  // the attribute wsdlLocation is ignored at the time of annotation   
>     processing of @WebService
>  DDEndpoint result = new DDEndpoint();
>       
>       result.setId(ep.getShortName());
>       result.setAddress(ep.getAddress());
>       result.setImplementor(ep.getTargetBeanName());
>       result.setMtomEnabled(isMtomEnabled(ep.getTargetBeanClass()));
>       result.setEpClass(seiClass != null ? seiClass : sepClass);
>       result.setPortName(new QName(serviceNS, portName));
>       result.setServiceName(new QName(serviceNS, serviceName));
>       Map<String, Object> props = new HashMap<String, Object>();
>       for (String k : ep.getProperties()) {
>          props.put(k, ep.getProperty(k));
>       }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira