At 09:22 AM 5/5/00 -0700, you wrote:
>What I'd like is a way to hand the parser an XML Stream or
>Reader, and have it return ECS data structures (for instance XMLDocument).
It strikes me that one difficulty with this would be the usual one with
decompilation, though worsened by the circumstance that you'll be
decompiling an execution trace rather than a script per se. The XML (or
HTML) is essentially the result of executing some (possibly mental) code
logic phrased in terms of a data environment accessed with variable naming
conventions and a code structure. Decompiling won't restore the
environment or logic per se. There won't be any larger data environment -
only what was realized in the ML stream. There won't be any variables
following some logical set of naming conventions, and if something was
generated by a conditional or looping structure, you won't see the
alternative conditions or the looping structure.
On the other hand, the results will certainly not be useless, even if some
fairly massive tranasformation of them might be a lot more useful.
The difficulty outlined cuts to the heart of a problem with HTML/XML per
se, I think, which is that it is specified without a scripting
facility. Hence the various *SP and external generator projects (like
ECS). I guess this is what happens when you think of text generation as
word processing instead of programming. :=)
John E. Koontz
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
