Dear All,
I am almost ready to commit a new version of FileWritingTransformer.
There is a new experimental/demo file-editor called <slash-edit/>.
I updated the transformer to try and stop it overwriting files when there
is an error. I now write into a temp file (which blocks) and rename it when
done.
This does not stop the problem of catching invalid XML submitted in forms
however.
I am using the StreamGenerator to capture the edited XML from a whole file.
When it's Parser finds non well formed XML, it throws a ProcessingException
and the FileWritingTransformer does not get to know anything about it.
Valid XML still gets happily written to disk, but missing everything after
the faulty tag.
The StreamGenerator could be modified, but I prefer the solution of writing
a RequestParsingGenerator, that can selectively parse any number of form
fields and won't throw ProcessorExceptions but encapsulate defective XML
fields as character data, with an error message in the Stream.
Does this make sense?
What I cannot work out is, would defective XML markup, passed down the
stream as character data, then transformed into a form to re-edit and fix,
be real tags or would they be Entities by then?
If they have been converted to Entities and you fix and re-post, they will
be written as Entities, no?
Thanks for any help
regards Jeremy
--
___________________________________________________________________
Jeremy Quinn Karma Divers
webSpace Design
HyperMedia Research Centre
<mailto:[EMAIL PROTECTED]> <http://www.media.demon.co.uk>
<phone:+44.[0].20.7737.6831> <pager:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
