So, to try and answer my own question (and you might very well correct me here, if I am wrong :-))
> But why does the FooService actually need the wsdlUrl again? I can see it > resolves it. I thought, that when i chose the path of generating classes > from WSDL to java, I had done all the wsdl access I needed to do offline. Could it be because what wsdl2java generates is only interfaces, annotated with jax-ws annotations. Hence, the cxf runtime use this to, at runtime, generate the calls? If this is correct, isn't there any way to get around this. As in, having the implementation code, that can call my webservice, generated "offline". So that I will NOT need to access my wsdl in production? /Per
