Elliotte Rusty Harold wrote:
>  J2ME by its nature is riddled with incompatibilities. It subsets many 
>  APIs, not just SAX. THe question here is which classes should be picked 
>  out of JAXP for the J2ME subset. Eliminating SAXParser/SAXParserFactory 
>  and adding XMLReader/XMLReaderFactory would be no more incompatible than 
>  the reverse.

+1. JAXB has introduced enough trouble with the default settings of the 
parser (does not match the SAX2 defaults) and the 
SAXParser/SAXParserFactory combo. It was really confusing for developers 
(me included) compared to SAX2, something that has not changed just to 
keep compatibility with it's initial versions.

IMHO J2ME is a still fresh enough to get right early.

-- 
Manos Batsis

Netsmart S.A.

Snail mail:
Panepistimiou 58,
10678, Athens, Hellas

URL:    http://www.netsmart.gr
Email:  mbatsis at netsmart dot gr
Tel:    (+30) 210 33 02 608
Fax:    (+30) 210 33 02 658
FOAF:   http://forte.netsmart.gr/foaf/manos_foaf.rdf





-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>