The File Serializer in 2.0 beta is fully configurable. The one in 1.5.2 is not. You can put a content-type element in the configuration. Possible values are text/html, text/xml and text/plain. You also have the following elements: public-doctype, system-doctype, encoding, indent and indent-amount.
Regarding the second problem: when a processor doesn't have any output, it's start() method must be implemented. Alex is working on an example and is going to send it as soon as it is completed.
-Erik
Bob Daly wrote:
> We're trying to develop a simple prototype using OXF, and it's going to > rely on the file system for storage. The bundled file serializer writes > an HTML header to the file no matter what, but we need to write & read > XML docs (the <content-type> tags seem to have no effect) . I guess my > first question is whether or not there is a way around this file > serializer HTML header issue. > > A custom processor has been written to write XML docs to disk, but I > haven't been able to successfully get this to work either. The class > extends SimpleProcessor and simply attempts to write a file containing > the instance doc passed in. All debug statements in the .xpl before and > after the call to the custom processor do not output to catalina.out. > Since there is no output back to the calling .xpl, is it necessary to > have an output parameter? At this point I'm not able to even verify > that the processor is being called. An entry to processors.xml was made > and the processor .jar was placed in the WEB-INF/lib directory, and > there are no complaints from or errors generated from oxf. > > Any comments or suggestions are welcomed, thanks! > > -bob daly > > _______________________________________________ > oxf-users mailing list > [EMAIL PROTECTED] > http://mail.orbeon.com/mailman/listinfo/oxf-users
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
