mrglavas    2003/11/14 10:38:45

  Modified:    java/docs faq-grammars.xml
  Log:
  Update references to PSVI packages, and fix
  reference to the default configuration.
  
  Revision  Changes    Path
  1.6       +3 -3      xml-xerces/java/docs/faq-grammars.xml
  
  Index: faq-grammars.xml
  ===================================================================
  RCS file: /home/cvs/xml-xerces/java/docs/faq-grammars.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- faq-grammars.xml  13 Jan 2003 15:34:30 -0000      1.5
  +++ faq-grammars.xml  14 Nov 2003 18:38:45 -0000      1.6
  @@ -312,7 +312,7 @@
       <p>
           For SAX and DOM the case is simple.  Just do:
       </p>
  -    <source>XMLParserConfiguration config = new StandardParserConfiguration();
  +    <source>XMLParserConfiguration config = new &DefaultConfig;();
   config.setProperty("http://apache.org/xml/properties/internal/grammar-pool";,
       myFullGrammarPool);
   (SAX|DOM)Parser parser = new (SAX|DOM)Parser(config);</source>
  @@ -349,7 +349,7 @@
           No such API exists at the current moment for DTD's.  For
           XML Schemas, there is a Xerces-specific schema component
           model API.  For details, it's best to look at the javadocs for
  -        the <code>org.apache.xerces.impl.xs.psvi</code>
  +        the <code>org.apache.xerces.xs</code>
           package.  Assuming you have produced a Grammar object from an XML Schema
           document by some means, to turn that object
           into an object usable in this API, do the following:
  @@ -362,7 +362,7 @@
               Call the <code>toXSModel()</code> method on the casted object;
           </li>
           <li>
  -            Use the methods in the 
<code>org.apache.xerces.impl.xs.psvi.XSModel</code>
  +            Use the methods in the <code>org.apache.xerces.xs.XSModel</code>
               interface to examine the new object; methods on this
               interface and others in the same package should allow you to access
               all aspects of the schema.
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to