Elliotte Harold wrote:
Peter B. West wrote:
But of course, I'm talking about Folio, which was built on a
pull-parsing model before I had ever heard of pull-parsing, because it
was the screamingly obvious thing to do. It gives me acute pleasure
to see my original design decisions vindicated
Elliotte Harold wrote:
Peter B. West wrote:
Fopsters,
Some of you may be aware of the activity going on around StAX. Java
1.6 (Mustang) was to have included JAXP 1.4, but that looks to be on
hold until Dolphin. However, StAX will be part of it, and soon
enough, SAX will be a dim memory.
Peter B. West wrote:
So I exaggerated. But how many better applications can you find me for
StAX than processing XSL-FO? If StAX has no application here, it has no
application. Is that what you're saying?
You're asking the question backwards. We should not be asking, Is
XSL-FO the best
Elliotte Harold wrote:
Peter B. West wrote:
So I exaggerated. But how many better applications can you find me for
StAX than processing XSL-FO? If StAX has no application here, it has no
application. Is that what you're saying?
You're asking the question backwards. We should not be
Peter B. West wrote:
But of course, I'm talking about Folio, which was built on a
pull-parsing model before I had ever heard of pull-parsing, because it
was the screamingly obvious thing to do. It gives me acute pleasure to
see my original design decisions vindicated by the the development
Peter B. West wrote:
Fopsters,
Some of you may be aware of the activity going on around StAX. Java 1.6
(Mustang) was to have included JAXP 1.4, but that looks to be on hold
until Dolphin. However, StAX will be part of it, and soon enough, SAX
will be a dim memory.
Yeah, right. I give
