• To: Elliotte Rusty Harold <elharo@m...>
• Subject: Re: Sun is forking SAX
• From: "Emmanuil Batsis (Manos)" <mbatsis@n...>
• Date: Mon, 21 Jul 2003 14:06:56 +0300
• Cc: "K. Ari Krupnikov" <ari@c...>, xml-dev@l...
• In-reply-to: <p04330100bb417375796b@[192.168.254.4]>
• Organization: Netsmart S.A., Greece
• References: <p04330107bb405e04435e@[192.168.254.4]><m33ch08o83.fsf@t...> <p04330100bb417375796b@[192.168.254.4]>
• Reply-to: mbatsis@n...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4)Gecko/20030624

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

• References:
  • Sun is forking SAX
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: Sun is forking SAX
    • From: ari@c... (K. Ari Krupnikov)
  • Re: Sun is forking SAX
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: Sun is forking SAX
• Next by Date: An approach to describing the relationships between units-of-measure
• Previous by thread: Re: Sun is forking SAX
• Next by thread: Re: Sun is forking SAX
• Index(es):
  • Date
  • Thread