Closed bilgehanm closed 8 years ago
Does this naming standard break something or cause an issue? I can't specifically remember if this was intentional or incidental, but it hasn't specifically caused issues with our projects other than the duplication of the work Service in on the wsdl page.
With a new project, no problem with the naming but for existing projects with lots of end user web service clients, each client had to update stubs.
I checked the wsdl, previously a service definition like:
`
Released 3.1.0
Thanks, just a quick note, if you don't provide a name property to a service, it still has duplicate Service string in service name (CarServiceService but documentation says CarService), but if you provide an endpoint name, it correctly creates the service with just single Service string in the name.
@GrailsCxfEndpoint(name='CarService')
class CarService {
result: CarService
@GrailsCxfEndpoint
class CarService {
result: CarServiceService
I create an grails 3.2 application add cxf dependency, create a DemoService
import grails.transaction.Transactional import org.grails.cxf.utils.GrailsCxfEndpoint import javax.jws.WebMethod import javax.jws.WebResult
@Transactional @GrailsCxfEndpoint class DemoService {
}
Run the project, and service is created as DemoServiceService instead of DemoService.
Same with grails-cxf-demo project.