Hi Martin, All

I've run into the known issue in SOAP-WSDL (using 2.00.10) regarding the lack of support for recursion. (Problem noted by that 'Deep recursion on....' message that appears when attempting to compile a .wsdl with wsdl2perl.)

From reading other posts in the forum I tried using the 'Typemap' branch to get around the problem, which did avoid the 'recursion' failings, but it also resulted in only creating 'Interfaces', no Element information for example is generated.

However, if I use the 2.00.10 release instead of the 'Typemap' branch, then Element classes are created.

(I see the difference because I have multiple .wsdl's to compile to test this, not all of which expose the recursion limitation)

Does anyone know of a workaround or a later/different branch to try?

>Did you find a solution to this?
Unfortunately no, I haven't found a solution or workaround to the problem.

The code generated from the 'Typemap' branch creates references to 'Element' classes, but doesn't
appear to create those classes.
Since the 2.00.10 tag, and versions prior create the elements for all my .wsdl files, I wasn't expecting to have a "can't create classes' bug" to appear in the typemap branch.

Since I haven't managed a workaround
for the 'Typemap' branch to generate classes
other then interface, I decided to experiment
with the XML::Compile::SOAP / XML::Compile::WSDL11 modules.
and success! (Although there seems to be a bug in those modules
related to hexBinary type, it was workable)

XML::Compile however doesn't provide a wsdl2perl type of code generator,
which is my preferred way to create my needed set of APIs.

I'm looking forward to trying out updates to SOAP::WSDL when these
issues with deep recursion, and class generation are solved.