Look at the options for jaxws:endpoint <- If that is how you publish it.
On Jul 23, 2010, at 12:27 PM, devaughn wrote: > Anyone have any ideas on this? Not sure if I am just misunderstanding how I > should be able to access it or if there is a configuration issue or perhaps > a container issue. > > -Dennis > > > On 7/22/10 10:18 AM, "Dennis Vaughn" <[email protected]> wrote: > >> Yes I have the wsdlLocation set and cxf recognizes that because I can invoke >> the service. I just can not access the wsdl like >> http://localhost:8080/service?wsdl >> >> -Dennis >> >> >> On 7/22/10 9:37 AM, "Johan Edstrom" <[email protected]> wrote: >> >>> Did you try wsdlLocation=classpath:mywsld.wsdl >>> >>> On Jul 22, 2010, at 10:18 AM, devaughn wrote: >>> >>>> I have a class annotated with WebServiceProvider and I am providing a wsdl >>>> in the jar and have it mapped appropriately according to endpoint and >>>> service names in my bean.xml. I can invoke the service without issue, but >>>> I >>>> can’t seem to retrieve the wsdl when it is deployed. If I do not specifcy >>>> the wsdl then it generates a wsdl according to the methods in the provider, >>>> which is invoke, but if I define one I am not able to retrieve it. I am >>>> running cxf 2.2.6 in a servicemix 4.2 container. Any thoughts? >>>> >>>> -Dennis >>> >>> Johan Edstrom >>> >>> [email protected] >>> >>> They that can give up essential liberty to purchase a little temporary >>> safety, >>> deserve neither liberty nor safety. >>> >>> Benjamin Franklin, Historical Review of Pennsylvania, 1759 >>> >>> >>> >>> >>> >> > Johan Edstrom [email protected] They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety. Benjamin Franklin, Historical Review of Pennsylvania, 1759
