Holk, David A wrote:
This is what is in my XML before FOP gets it:
<attribute>&lt;/= 1.5%</attribute>
Looks like the double escaping you mentioned.
Exactly.
Here is the total flow:
---------------
Retrieve data from Oracle as string using XML SQL utility
Parse into java classes using SAX (at this point I replace '<' with '<'
in my SAX event handler's end Element event)
What "java classes"? A DOM? If so, you can pass it to the
transformer using a DOM source, no need to serialize the
stuff.
I almost seems like I don't need to do the '<' to '<' replacement, in the
EventHandler. But FOP was choking if I didn't. SAX must be doing some
additional transformation, maybe after endDocument?
FOP doesn't choke, it's the parser somewhere. SAX is an API,
it doesn't do any transformation on itself. If you find
a < in a SAX character event, it wont change magically
to a '<' downstream.
I guess your screw-up is somewhere in the "java classes"
construction/manipulation, you shouldn't have an
&lt; in the XML string.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
