hi,

it is some time we did any modification to XmlPull API 1.1 (it is
remarkably stable) but there are few minor issues and improvements
recorded over years (and J2ME devices get bigger memory nowadays ...) so
it looks like good time for incremental release i.e. 1.2

based on list of issues and improvements (RFE) in bugzilla two stands out:

1) http://www.extreme.indiana.edu/bugzilla/show_bug.cgi?id=167
skipSubTree() looks like a very useful method to have implemented in
parser (skipping can be fast) - that would add to XmlPullParser method:
/**
* Skip sub tree on which the parser is currently positioned on.
* <br>NOTE: parser must be on START_TAG and when function returns
* parser will be positioned on matching END_TAG
*
* This method is typically optimized by parser but the its logic
should follow this:
* <code>
* require(XmlPullParser.START_TAG, null, null);
* int level = 1;
* while(level > 0) {
* int eventType = next();
* if(eventType == XmlPullParser.END_TAG) {
* --level;
* } else if(eventType == XmlPullParser.START_TAG) {
* ++level;
* }
* }
* </code>
*/
public void skipSubTree() throws XmlPullParserException, IOException;



2) http://www.extreme.indiana.edu/bugzilla/show_bug.cgi?id=240
this is long standing issue related to how setPrefix() works and how it
should be working more like xmlns:pref='...' (so digital signatures code
works well) - that would add to XmlSerializer three new methods with
prefix as an argument:

public XmlSerializer startTag (String prefix, String namespace, String
name)
public XmlSerializer endTag (String prefix, String namespace, String name)
public XmlSerializer attribute (String prefix, String namespace, String
name, String value)

if there are any other issues/improvements/etc please let us know (send
email to xmlpull-dev and log the issues in bugzilla)

both XPP3/5 and kXML2 plan to implement soon XmlPull API 1.2

thanks,

Alek Slominski (& Stefan Haustein)