Be sure you meet the minimum requirement of CLDC 1.1 and MIDP 2.0

Use the -cldc option with XBinder. This changes the generated code slightly. Rather than using classes that are not present in CLDC/MIDP, it uses replacement classes we have provided. For example, it uses com.objsys.javax.xml.datatype rather than javax.xml.datatype. The -cldc option also causes the generated code not to use language features that it normally would use, such as generics, or for each loops.

Use the xbrt_cldc.jar file. This is the XBinder runtime for Java ME CLDC/MIDP. It contains replacement classes for classes that are not otherwise present. The classes in this JAR have been pre-verified.

In folder <XBINDER_HOME>\java\xmlpull, we have provided a JAR for the XmlPull API (www.xmlpull.org), and a pared-down JAR of the kXML implementation of this API. Include the API on your classpath, and deploy both as part of your Java ME application.

The XBinder generated code will accept an XmlPullParser for use in parsing XML. Be sure to use a namespace aware parser.