At 08:51 AM 2/26/03 -0800, you wrote:
Another possibility is to take that <xsd:schema> node you've found, and use the Xerces PSVI DOM and Grammar interfaces (see the FAQ about using grammars in the Xerces distribution). Essentially, you can serialize the schema node to a string, use the grammar preparser to build a SchemaGrammar from it, convert it to an XSModel, and then rummage around in that, finding the various element, type and attribute definitions, with all their various properties and facets -- the whole structure of the schema as expressed in the PSVI (post-schema-validation-infoset).
I'm doing this in a project I'm working on, and it works nicely.
Jeff
This seems a bit tricky, but should do the job. I've tried to search for some examples, but dosen't seem to be any around. Even the Xerces docs aren't usefull. :( Do you know any references, examples or HowTo's to start from?
Thank you very much, Xserty
----- Original Message ----- From: "Owen D Burroughs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 26, 2003 7:34 AM Subject: Re: WSIF, WSDL and Complex Types!
> Xserty, > > The Parser class in WSIF might help but it depends on what you want to > achieve. If you want to be able to find any of the elements/attributes in > the schema, the Parser code will not do this. It does not provide full > schema parsing functionality and there is no intention for it to do so. > What it can do, is find you all of the names of the global elements in the > schema and tell you if they are complexTypes, simpleTypes or Elements and > whether or not they represent Arrays. To establish any greater detail about > the types in the schema you would need to use a full schema parsing API > such as the one recently contributed to Axis or the one in eclipse. > > Owen
