XOM API for Processing XML with Java

[Elliotte Rusty Harold <elharo AT metalab.unc.edu>]

At 11:05 PM -0500 2/3/04, John Cowan wrote:

> One tactic is to use a big String, encoding each byte as a character.
> Be sure to generate them using \ddd octal escapes rather than \udddd
> Unicode ones, as the latter will cause syntax errors in certain cases.
> That bypasses the method-size problem.

Really? That's devious. I'm impressed. I'll consider that if the 
current getResourceAsStream approach causes problems for anyone.

Could this string be garbage collected after I'd decoded it into the 
byte array I really want? Or would I be carrying the same 64K of data 
around twice, once in a String and once in a byte array? In which 
case should I just hide the lookup table in the chars of a String 
rather than the bytes of an array in the first place?
--

  Elliotte Rusty Harold
  elharo AT metalab.unc.edu
  Effective XML (Addison-Wesley, 2003)
  http://www.cafeconleche.org/books/effectivexml
  http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA