One of the challenges is that the rules for schema are quite flexible,
which means that there are a wide variety of ways to accomplish the same
thing. Even if the schema only uses <sequence> compositors, for example
(i.e. no <choice>, <all>, <group>, no <complexContent>, mixed,
constraints, keys, ...) there are multiple ways to define the same
structure: "russian doll," ref, named types, or any combination of the
three, for example. If you want to develop a transform that works for
any valid schema, you will have to handle all the variations. Certainly
possible, but a lot of work.

If you can make assumptions about the schema, your task may be simpler,
possibly much simpler.

So, one question for you: Are you developing tools that are supposed to
work with any valid WSDL? Or are you developing tools that are only
required to work for some specific WSDLs?

Stephen


-----Original Message-----
From: Senthilkumaravelan K [mailto:skumaravelan@xxxxxxxxxxxxxx]
Sent: Wednesday, 14 March 2007 10:29 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Recursive Processor to find Type of complex type for
WSDL file

Hi Abel,
I need to find data type of all the elements of the message part.
for the given XML

 <wsdl:types>
...