All Implemented Interfaces:
ModifiableSource
All Known Implementing Classes:
AbstractStreamWriteableSource, FileSource
Use - the org.apache.excalibur.source.ModifiableSource interface instead
Callers will use the most appropriate method for their use and
it's up to the implementation to handle both sources. For example,
an XML-based implementation can use a parser to convert bytes written
to the OutputStream to SAX events, and a byte-based
implementation (such as file), can use a serializer to convert
SAX events to a byte stream.
< - a href="mailto:sylvain@apache.org">Sylvain WallezCVS - $Id: WriteableSource.java 433543 2006-08-22 06:22:54Z crossley $| Method from org.apache.cocoon.environment.WriteableSource Summary: |
|---|
| canCancel, canCancel, cancel, cancel, exists, getContentHandler, getOutputStream |
| Method from org.apache.cocoon.environment.WriteableSource Detail: |
|---|
ContentHandler returned by
#getContentHandler() be cancelled ? |
OutputStream returned by
#getOutputStream() be cancelled ? |
ContentHandler returned by
#getContentHandler() .
After cancel, the handler should no more be used. |
OutputStream returned by
#getOutputStream() .
After cancel, the stream should no more be used. |
|
ContentHandler where an XML document can
be written using SAX events.
Care should be taken that the returned handler can actually be a org.apache.cocoon.xml.XMLConsumer supporting also lexical events such as comments. |
InputStream where raw bytes can be written to.
The signification of these bytes is implementation-dependent and
is not restricted to a serialized XML document. |