Posted by
Colin O'Brien on
URL: https://discuss.orbeon.com/Serving-plain-text-tp26088p26102.html
Hello Erik and Eric
to wrap this up...
>
> Oh wait - you're saying use the text converter as well as the http
> serializer.
> I didn't try that (didn't see a mention of the converter on the
> serializer page)
> So the text converter will strip the <document> element.
> Except that the doc on text converter shows the <document> element
> still there in the output.
> But the doc does say this is how to get csv now.
> I will have to try it when I get to the office.
The combination of text converter and http serializer did produce just
the text I wanted.
I took the <docuemnt> element from the output of the text converter and
made it the wrapper element in my xslt and removed the text converter
and I still got what I wanted.
I'm sure I tried that combination yesterday and it didn't work - the
only difference I can detect is that when I defined the content-type I
omitted the semi-colon from content-type="text/plain;".
It's a harsh world :-)
So the docs are probably right in as much as what they say, but they
don't spell out that the serializers will strip wrapper elements when
they conform to the OPS non-xml document spec.
One thing that seems to be missing in the converter/serializer combo
compared to the legacy text serializer is the ability to suggest a name
for the file being downloaded.
It doesn't matter for what I am doing, since the file isn't intended to
be downloaded to the client file system, but I could see it being more
important with examples like csv.
Thanks once again for your help and the ever greater OPS system
Colin
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws