Jeni,
You're right: we know it's horrible, but comments don't go through
because processors strictly use the SAX ContentHandler interface to
communicate, and a SAX ContentHandler doesn't have support for
comments. The reason why SAX was "designed" that way is beyond me.
Funnily enough, this issue has almost never come up for us in years!
Propagating events properly would need refactoring to support also
LexicalHandler. I don't think it would be hard, just a little time-
consuming: creating an interface combining LexicalHandler and
ContentHandler and passing that around instead.
Mainly, the core of it is in ProcessorImpl. The following are obvious
methods which use ContentHandler:
ProcessorOutput.read()
ProcessorImpl.ProcessorOutputImpl.readImpl()
ProcessorImpl.readInputAsSAX()
-Erik
On May 12, 2009, at 4:26 AM, Jeni Tennison wrote:
> Hi,
>
> There doesn't seem to be a way of getting comments to pass between
> Orbeon processors, or indeed in Orbeon's output. Am I missing
> something? Is there a workaround? Is it likely to be fixed, and if
> not what's the rationale?
>
> Jeni
> --
> Jeni Tennison
>
http://www.jenitennison.com>
>
> --
> You receive this message as a subscriber of the
[hidden email]
> mailing list.
> To unsubscribe: mailto:
[hidden email]
> For general help: mailto:
[hidden email]?subject=help
> OW2 mailing lists service home page:
http://www.ow2.org/wws--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws
Locked
