With these parameters you can filter which <b>WSDL files</b> and <b>XML schemas</b> may be documented in <b>full details</b>
(which means generating WSDL File / XML Schema Overviews and documenting all components found in them).
<p>
<b><i>WSDL file</i></b> is considered any XML file containing
<code>&lt;wsdl:definitions&gt;</code> as a top element.
<p>
<b><i>XML schema</i></b> is identified by the <code>&lt;xs:schema&gt;</code> element
found either:
<ul>
<li>As a top element in an XML file. In that case, such an XML is called <b>XSD file</b>.</li>
<li>Within <code>&lt;wsdl:definitions&gt;/&lt;wsdl:types&gt;</code> element in a WSDL file.
In the last case, it is called <b><i>embedded schema</i></b>.
</li>
</ul>

All WSDL/XSD files come from the following locations:
<ul>
<li>The files specified initially with the generator arguments.</li>
<li>The files directly or indirectly referenced from the initial files (via
<code>&lt;wsdl:import&gt;</code>,
<code>&lt;xs:import&gt;</code>, <code>&lt;xs:include&gt;</code>, <code>&lt;xs:redefine&gt;</code> elements).</li>
</ul>
Although all involved WSDL files and XML schemas must be loaded and processed,
you may want actually to document only some of them.
With these parameters you can specify which.

<p>
<b>Notes:</b>
<ul>
<li>
The filtered out WSDL files and XML schemas (as well as the definitions/components found in them)
may still be mentioned in the documentation, however with few details.
</li>
<li>
XML schemas embedded in the filtered out WSDL files are excluded from full documenting as well.
</li>
</ul>