Thank you very much for your help.  This is a real improvement from my
ugly hack!

David Carlisle wrote:
> Scott Sauyet wrote:
>>  I would rather be using node-
>> sets.  But whenever I tried that, I ran into issues of variables that
>> held things that looked like but weren't really node-sets.
>
> result tree fragments. If using XSLT2 is an option then that particular
> problem goes away as rtf is no more (node sets are also gone) both
> replaced by sequences.

I honestly don't even know what XSLT processor I'm using, at the
moment; it's whatever default Ant 1.7 has when running on Java 1.6
(Xalan?).  I can switch to whatever I want, as this will just end up
part of the build process.  The actual problem is to reduce a WSDL
document to a smaller one based upon a parameter that lists the high-
level services to include.  I worked my way through the services,
bindings, port-types, and messages based upon that input parameter.
And, with some help from  the kind people on this list, I got the
initial list of the custom xs:simpleTypes and xs:complexTypes needed
to support the selected messages, but I then need to recursively work
through their dependencies.

As I said in my original message, I had this working, but wasn't happy
with the technique.  I'm glad to know that there is something better;
and I'll be updating my stylesheet soon with your suggestions.


> I'm not quite sure what output format you want but probably something
> like this in xslt1 will chase your dependencies

I actually need to output format to be identical to the input format,
just with a smaller set of elements chosen.  It was pretty simple to
modify your suggestion, though, to get that.  Thank you again for your
help.

  -- Scott