On 5/6/07, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
Why i don't use
writer.flush()
writer.write()
or
writer.writeText(null)
writer.write
... because
(A) it's an utter pain to demand that of all developers
any time they're calling write().
(B) flush() can have larger, undesired conseq
I've just found something in the spec/api (description for startElement):
"The element will be closed (i.e. the trailing > added) on any
subsequent call to
startElement(), writeComment(), writeText(), endDocument(), close(),
flush(), or write()."
So, I've to fix it in the TobagoResponseWriter
Why i don't use
writer.flush()
writer.write()
or
writer.writeText(null)
writer.write
If write() should close a starting element why is this not part of the
spec or javadoc?
Regards
Bernd
Adam Winer wrote:
No, write() calls must close a starting element.
Otherwise the following sequence:
No, write() calls must close a starting element.
Otherwise the following sequence:
... would fail.
-- Adam
On 5/4/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Udo,
I think you are right, since the write methods are inherited from
abstract Writer clazz.
Methods inherited f
Udo,
I think you are right, since the write methods are inherited from
abstract Writer clazz.
Methods inherited from class java.io.Writer
close, write, write, write, write, write
Therefore no need to close an open starting (HTML) element
-M
On 5/4/07, Udo Schnurpfeil <[EMAIL PROTECTED]> wro
Hi all,
I have detected a possible problem with the HtmlResponseWriterImpl.
The write(String) method closes the start tag if open, but the spec says:
6.4 ResponseWriter
[...]
It supports both low-level and high level APIs for writing character
based information
The ResponseWriter class extends
