Hi Matt,
> Because I will not be able to control the HTML that users enter (and
> eventually ends up in XML), I will probably have to scan all input html
for
> >, <, and & and replace them with their corresponding numeric
> entities &#xxx;. Unless castor translates numeric entities as well, it
> should work. Maybe this will work for you too.
I now put a dummy string in the object, and I replace it after marshalling
(using a FilterWriter). This works, but it's pretty dirty.
Your solution is much cleaner and I'd prefer to do the same.
Can you let me know if it works?
Thanks,
Michel
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
