CVS Update: xmlpull-api-v1/src/java/samples

aslom       02/07/25 11:10:51

  Modified:    doc      changes.html
               src/java/api/org/xmlpull/v1 XmlPullParserException.java
               src/java/samples BestDeal.java
  Log:
  updated list of changes
  
  Revision  Changes    Path
  1.29      +44 -8     xmlpull-api-v1/doc/changes.html
  
  Index: changes.html
  ===================================================================
  RCS file: /l/extreme/cvspub/xmlpull-api-v1/doc/changes.html,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -b -t -w -r1.28 -r1.29
  --- changes.html	2002/04/25 05:07:10	1.28
  +++ changes.html	2002/07/25 16:10:51	1.29
  @@ -9,8 +9,44 @@
   
   <H1>Changes to XMLPULL V1 API</H1><P>
   
  -<h3><span style="font-weight: 400"><a name="XMLPULL_1_0_8"></a></span>2001-04-24 (XMLPULL_1_0_8)</h3>
  +<h3>IN PROGRESS: <a name="XMLPULL_1_0_9"></a>2001-00 (XMLPULL_1_0_9)</h3>
   <ul>
  +<li><strong>NEW! XmlSerializer API</strong> that is now required part of
  +XMLPULL API on J2SE (on J2ME typically factory is not used and only implementation of
  +serializer or parser interface may be available).
  +
  +<li>added newSerializer() method to XmlPullParserFactory
  +
  +<li>added new FAQ entries:
  +
  +<ul>
  +
  +<li><a href="faq.html#API_DESIGN">Why is there only one "large" interface, 
  +wouldn't it be cleaner to use event objects and polymorphism?</a>
  +
  +
  +<li><a href="faq.html#3NEXT">What is the difference between 
  +<tt>nextToken()</tt>, <tt>next()</tt>, <tt>nextTag()</tt>, and <tt>nextText()</tt>?</a>
  +
  +<li><a href="faq.html#NEXT_MOTIV">Why are there different <tt>next()</tt> methods, wouldn't it be cleaner to
  +have a set method, allowing me to specify the type of events I am interested in
  +in general?</a>
  +
  +</ul>
  +
  +
  +
  +<li>list of class names with factory, serializer and/or parser must be now 
  +separated by colon in XMLPULL tests property (<code>org.xmlpull.v1.tests</code>), for example:
  +<code>-Dorg.xmlpull.v1.tests=DEFAULT:org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer</code>
  +
  +<li>changed XmlPullParser constants to  be all consistently <samp>int</samp> (few were declared as 
  +<samp>byte</samp> ...)
  +
  +</ul>
  +
  +<h3><a name="XMLPULL_1_0_8"></a>2001-04-24 (XMLPULL_1_0_8)</h3>
  +<ul>
   <li><b>two API changes are not backward compatible</b> with 1.0.7:
   <ul>
   <li><b>readText</b>() function was <b>removed</b>, please use nextText() instead
  
  
  
  1.11      +1 -1      xmlpull-api-v1/src/java/api/org/xmlpull/v1/XmlPullParserException.java
  
  Index: XmlPullParserException.java
  ===================================================================
  RCS file: /l/extreme/cvspub/xmlpull-api-v1/src/java/api/org/xmlpull/v1/XmlPullParserException.java,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -b -t -w -r1.10 -r1.11
  
  
  
  1.3       +5 -0      xmlpull-api-v1/src/java/samples/BestDeal.java
  
  Index: BestDeal.java
  ===================================================================
  RCS file: /l/extreme/cvspub/xmlpull-api-v1/src/java/samples/BestDeal.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -b -t -w -r1.2 -r1.3
  --- BestDeal.java	2002/07/24 17:39:49	1.2
  +++ BestDeal.java	2002/07/25 16:10:51	1.3
  @@ -3,6 +3,11 @@
   import java.util.*;
   import java.text.MessageFormat;
   
  +/**
  + * Rewritten http://www-106.ibm.com/developerworks/xml/library/x-saxapi/listing4.html
  + * to make easy to comapre how to "natutal is to manage state with SAX and with XMLPULL API.
  + * For details see: http://www-106.ibm.com/developerworks/xml/library/x-saxapi/
  + */
   public class BestDeal {
   
       protected static final String MESSAGE =