Re: How to handle string data > 32767 bytes, keyed data queue access, how to store login credentials

Pete Hall wrote:

String data > 32767 bytes:
I'm working a web service that returns an XML document. What would be
the preferred way to return a document that is larger than 32767 bytes?
Is there a magical way to plug a stream writer into a clob or something
similar? I think I can work around it this time, but I'm sure it will
become an issue at some point. I'm interfacing with an IIS web site, so
I need something that's not totally hostile to Windows.

I think I've worked this out, although I haven't got it working yet. You
save the CLOB to a file in a temp directory on the server, then redirect
to it. It appears that's the only way an XML document can be delivered,
because the http response writer isn't available. It must be done with a
REST service, not SOAP, in order to avoid embedding a valid xml document
with its doctype and optional xml template directive in another XML,
where the doctype and xml template directive are invalid. Anyone got a
better way? BTW, the CLOB methods validate in the RBD editor, but don't
work unless you qualify all method calls, even if you import lobLib.
What's up with that?