It's only rough at the moment but I got it working nicely with a feature. I can get rid of the wsdlLocation, serviceName and namespace stuff
https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/main/java/com/pellcorp/server/ClientConfigFeature.java On Thu, Feb 21, 2013 at 2:09 PM, Jason Pell <[email protected]> wrote: > I can get hold of the wsdl manager to load wsdl and I figure I need to then > update the client service model with DescriptionInfo and extension policy > refs where required so that the wsdl11attachment provider can load them > Is there any other way? > > Sent from my Galaxy S2 > > On Feb 21, 2013 12:35 PM, "Jason Pell" <[email protected]> wrote: >> >> Hi, >> >> I know I can use wsdlLocation to get the ws-policy stuff applied. >> What I was hoping is that I could somehow delay this until I get to a >> jaxws:client feature and apply it then by loading it from the wsdl. >> >> In this way I don't need to have the wsdlLocation in the jaxws:client >> definition or a @Annotation, but can let a feature control it. >> >> I can set the address of the client with a feature, but not being able >> to set the wsdlLocation or at least set the WS-Policy stuff >> makes being able to set the address in the feature pretty pointless. >> >> Thanks for any advice
