Wsdl

[Alp Timurhan Çevik <at...@gmail.com>]

I am experiencing some trouble regarding WS-I interoperability. The main
problem is using cxf web services from .net.

Wsdl-first approach is being used to create web services. The wsdl supplied
is WS-I compatible (I am checking it using WS-I tools). I have no trouble
using this wsdl with cxf nor .net.

After publishing the service using wsdl2java generated code, the
http://url/url?wsdl presents a different wsdl document, reconstructed
somehow.
And this new generated wsdl document is has BP2102 failure, which is related
to wsdl files including other wsdl files (actually the wsdl generated at
runtime is importing another wsdl document, also generated at runtime. The
original wsdl also has import, but it is importing xsd files, not wsdl
files.)

So, what I would like to do, is to have a working wsdl accessed from
http://url/url?wsdl which may be achieved by
* presenting the original wsdl file
* making runtime generated wsdl workable somehow by
** forcing cxf to generate a single wsdl, not one using includes
** forcing cxf to use xsd imports
** trying to resolve the imported wsdl's namespace issue (actually not sure
if the real problem is the case)

though do not know how to achieve any, looked around a bit but could not
find a solution.

Happy new year,
Alp

Re: Wsdl

[Christian Schneider <ch...@die-schneider.net>]

Hi Alp,

you can advise cxf to use the wsdl you provide (wsdlLocation in endpoint 
definition). When you do contract first you schould never use the wsdl 
generated by cxf. Instead always use the wsdl you constructed by hand.

Another solution is to not use the wsdl from cxf and instead always use 
a repository. In my company we use the maven repository for this. (see 
http://www.liquid-reality.de:8080/display/liquid/2009/09/03/Use+maven+repository+as+a+service+repository). 
Of course there are many other repository solutions.

Greetings

Christian




Alp Timurhan Çevik schrieb:
> I am experiencing some trouble regarding WS-I interoperability. The main
> problem is using cxf web services from .net.
>
> Wsdl-first approach is being used to create web services. The wsdl supplied
> is WS-I compatible (I am checking it using WS-I tools). I have no trouble
> using this wsdl with cxf nor .net.
>
> After publishing the service using wsdl2java generated code, the
> http://url/url?wsdl presents a different wsdl document, reconstructed
> somehow.
> And this new generated wsdl document is has BP2102 failure, which is related
> to wsdl files including other wsdl files (actually the wsdl generated at
> runtime is importing another wsdl document, also generated at runtime. The
> original wsdl also has import, but it is importing xsd files, not wsdl
> files.)
>
> So, what I would like to do, is to have a working wsdl accessed from
> http://url/url?wsdl which may be achieved by
> * presenting the original wsdl file
> * making runtime generated wsdl workable somehow by
> ** forcing cxf to generate a single wsdl, not one using includes
> ** forcing cxf to use xsd imports
> ** trying to resolve the imported wsdl's namespace issue (actually not sure
> if the real problem is the case)
>
> though do not know how to achieve any, looked around a bit but could not
> find a solution.
>
> Happy new year,
> Alp
>
>