On Friday 05 November 2010 7:51:19 pm Yonghe wrote:
> Hi,
>
> I am trying to create a WS-Trust client for .net 4.0. However, CXF's
> wsdl2java reports stack overflow while parsing the wsdl from .net's
> SecurityTokenService.
What version of CXF? 2.3.0 seems to not stack trace, but doesn't actually
work either:
WSDLToJava Error: Non-unique body parts! In a port, operations must have
unique operation signatures on the wire for successful dispatching. In port
{http://schemas.microsoft.com/ws/2008/06/identity/securitytokenservice}WS2007HttpBinding_IWSTrust13Sync,
operations
"{http://schemas.microsoft.com/ws/2008/06/identity/securitytokenservice}Trust13Cancel";
and
"{http://schemas.microsoft.com/ws/2008/06/identity/securitytokenservice}Trust13Renew";
have the same request body block {http://docs.oasis-open.org/ws-sx/ws-
trust/200512}RequestSecurityToken
If you try the RI's wsimport, you get similar messgaes:
[WARNING] Non unique body parts! In a port, as per BP 1.1 R2710 operations
must have unique operation signaure on the wire for successful dispatch. In
port WS2007FederationHttpBinding_IWSTrust13Sync, Operations "Trust13Validate"
and "Trust13Cancel" have the same request body block {http://docs.oasis-
open.org/ws-sx/ws-trust/200512}RequestSecurityToken. Method dispatching may
fail, runtime will try to dispatch using SOAPAction
line 112 of file:/tmp/sts.wsdl
although it does proceed to generate code that may or may not work.
> Here is the wsdl
> http://cxf.547215.n5.nabble.com/file/n3252672/sts.zip sts.zip . I would
> like to know what is wrong with the wsdl? or, it is a bug of wsdl2java?
Basically, the STS wsdl is not a WSI-Basic Profile compliant wsdl and thus
doesn't map onto JAX-WS interfaces very well at all. My suggestion would be
to use the STSClient object that CXF already has built in and seeing if that
would work for you.
--
Daniel Kulp
[email protected]
http://dankulp.com/blog
