Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320175 - REST services shouldn't be constrained to text types
Summary: REST services shouldn't be constrained to text types
Status: RESOLVED FIXED
Alias: None
Product: ECF
Classification: RT
Component: ecf.remoteservices (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.6.0   Edit
Assignee: Scott Lewis CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-17 12:50 EDT by Alex Blewitt CLA
Modified: 2013-03-04 12:22 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Blewitt CLA 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 CLA 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.