restfuse 1.1.1 released
It has been almost a year since the last restfuse news. In the meantime restfuse was adopted by a lot of individuals and companies. Since the last release the development continued on github and made it now worthwhile to publish an update. Last week we released restfuse 1.1.1. Some noteworthy things are:
- Updated the underlying Jersey version to 1.13
- Dynamic request manipulation (currently only the headers, but open for extension). Thanks to drejc for the contributions.
- Added missing HTTP status codes.
- Extension of the asynchronous services testing facilities. Restfuse now also supports poll in addition to webhooks.
The new version has already been published to Maven central. Use this code to embed it:
<dependency> <groupId>com.restfuse</groupId> <artifactId>com.eclipsesource.restfuse</artifactId> <version>1.1.1</version> </dependency> |
Version 1.1.1 can also be downloaded as binaries from the brand new restfuse website or consumed via p2 (yes, it’s an OSGi bundle). Any feedback is very welcome 
4 Responses to “restfuse 1.1.1 released”
4 responses so far
Written by Holger Staudacher. Published in Categories: EclipseSource News, Planet Eclipse
Written by Holger Staudacher. Published in Categories: EclipseSource News, Planet Eclipse
Do you have a sample of including the dependency in an ant build.xml file
Hi PG, no I haven’t. I have opened an issue to provide one for the next release. If you have successfully embedded restfuse in you ant build I would appreciate a comment on the issue with an example
https://github.com/eclipsesource/restfuse/issues/23
Thanks! Cheers Holger
I have gone through the Restfuse docs.
One thing I have noticed is that the annotations are all assuming that a single restful request is going to be issued per test case, and there is no support for multiple web service calls with annotation.
If so, it would be impossible to use Restfuse for workflow test where multiple requests need to be issued.
Or do I have this wrong?
Hi Red,
the assumption is one request per test case. We are on our way to support Test Method Chaining. This enables you to test services that match with the Richardson Maturity Model Level 3.
Cheers holger