Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320175

Summary:	REST services shouldn't be constrained to text types
Product:	[RT] ECF	Reporter:	Alex Blewitt <alex.blewitt>
Component:	ecf.remoteservices	Assignee:	Scott Lewis <slewis>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	slewis, wim.jongman
Version:	unspecified
Target Milestone:	3.6.0
Hardware:	All
OS:	All
Whiteboard:

Description Alex Blewitt

2010-07-17 12:50:16 EDT

Build Identifier: 

There's an implicit assumption that the REST service will be some kind of String. Regardless of its encoding, that isn't always the case - for example, REST services might include streaming back some JPG or PNG bytes that form an image, or a repository system hosting non-textual content.

Reproducible: Always

Comment 1 Scott Lewis

2013-03-04 12:22:02 EST

Fix pushed to master

http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/commit/?id=28b9df08b0f707211b2d1f84d20135c87b5fdc86

This changes the IRemoteResponseDeserializer interface to have a byte[] rather than String as last argument...along with all clients.  This is a breaking API change as discussed on the ECF dev mailing list on this thread:

http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg06200.html

The major version of the API bundle that encloses this interface was updated, because this is a breaking API change.

This fix will be in ECF 3.6.0, due on March 11.