← Prev in month
← Prev in thread
Next in thread →
Next in month →
[wsrp-wsia] [I#191] Returning binary data from getMarkup is notsupported wel l
Issue: 191 Status: Active Topic: interface Class: Technical Raised by: Andre Kramer Title: Returning binary data from getMarkup is not supported well Date Added: 18-Dec-2002 Document Section: v0.85/5.1.8 Description: "A producer wishing to return binary MIME data can do so by specifying a binary markup type in markupContext.markupType but must return the markup as ""string markup"" in MarkupContext. It is unclear how the data is encoded as a string (i.e. not specified by WSDL) and the Web stack is not leveraged. A related problem area is that of allowing the consumer to specify MarkupParams.markupCharacterSet versus the char encoding actually used by the Web method." Resolution: "Allowing MarkupContext.markup to be base64 rather than always encoded to a string would address both issues and allows Web stacks to do the heavy lifting. Suggest replacing: <element name=""markupType"" type=""xsd:string"" minOccurs=""0""/> <element name=""markup"" type=""xsd:string"" minOccurs=""0""/> with: <element name=""markupType"" type=""xsd:string"" minOccurs=""0""/> <element name=""markupString"" type=""xsd:string"" minOccurs=""0""/> <element name=""markupBytes"" type=""xsd:base64Binary"" minOccurs=""0""/> This scheme de-seralizes bytes to/from byte[]. It can be readily mapped to an attachment (once WSDL support is more ubiquitous). Unfortunately, not all stacks support <choice/> so we can't use that more natural representation but the above does not waste any bandwidth as the elements are minOccurs=""0""."
← Prev in month
← Prev in thread
Next in thread →
Next in month →