This quesiton refers to the RESTeasy framework by jboss.
I'm using the client framework to call a third-party REST webservice. I was wondering if the RESTeasy framework has support to produce application/zip contents.
I've read the documentation, and I don't see any mention of that. Does RESTeasy provide the tools to handle a application/zip response (from a third-party Web service for example) ?
Can someone put me on the right direction ?
This annotation did the trick for me :
#GET
#Produces("*/*")
#Path("/api/{language}.zip")
public File getSerieBaseInformation(#PathParam("language")String language);
Related
We use Apache CXF in our application with jax-rs to build REST Api. As of now, there is no documentation about the various endpoints available and is deployed on Tomcat 8.5 server.
I have done some R&D on how to find a solution. I understand that Swagger can be used.
But, I did not find enough documentation to user swagger with Apache CXF.
I understand that these type of questions are prohibited in the site. At the same time, I am not sure which chat room to use for this purpose.
Any information on this would help me a lot.
Depending on the CXF version that you are using, I would suggest to use OpenApiFeature (OpenAPI is newer than Swagger) as described here: http://cxf.apache.org/docs/openapifeature.html
You can also find multiple sample projects with Swagger or OpenAPI here: https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jax_rs
I developed a dynamic web project in eclipse java EE ide as index.jsp, when I run it on Tomcat Server7.0 server it says http://localhost:8080/filename/ something. is that what they mean by REST? or do I need Spring to run a REST ?. rest is what that comes in a url, if i provide this url in my browser it opens the file, then why I can't call it as rest service?
Restful is an architectural style that make in disposition through HTTP a number of resources under different formats, usually json, to set or retrive the ressources, simple http operations (PUT, GET, POST, and DELETE. PUT) could be used for that.
I recommend you to use JAX-RS, but here u can see how to work with rest web service with Spring:
Building a RESTful Web Service Spring
Do RESTEasy, Jersey or Restlet integrate client sided caching?
I read something about a CacheClient for Jersey
Is that an official implementation? If not, are they working on Client Caching for Jersey 2.0? Can someone confirm this?
For Resteasy I read here something about official client sided cache control.
Im not sure about Restlet. Are there some official good solutions?
Regarding Restlet, we are planning to add a caching service in version 2.2. That will benefit the JAX-RS extension as well.
See our detailled roadmap here.
I have an application using Apache CXF with a lots of SOAP services implemented. So, i would like to use the "service registry" concept and then, i´d hear about UDDI, but i dont know how to implemented that.
Is Apache CXF already composed by an API to deploy UDDI engine or should i fix another library to do that?
Take a look at JUDDI:
http://juddi.apache.org/
which is a UDDI service. The latest version is written to JAX-WS and is tested by default with CXF.
To add, jUDDI has a neat way to automate the registration of web services using annotations and a servlet startup listener.
Source: http://svn.apache.org/repos/asf/juddi/trunk/juddi-examples/uddi-annotations/
I am using Jersey 1.9 and it is generating my WADL perfectly except I need to redefine the resources base URI.
I'm running Jetty 7 sitting behind Apache using mod_proxy as a reverse proxy to route REST requests back to Jetty / Jersey. So Jersey generates the resources base URI as
http://localhost:8080/testRestAPI/rest/
when I need something like
http://mydomain.com/rest/
I found this from Google but it is not working: http://jersey.576304.n2.nabble.com/Changing-baseURI-when-generating-WADL-td6169703.html
unfortunately, you've found a bug in Jersey implementation. Please file a new issue as stated on mailing list - jira link: http://java.net/jira/browse/JERSEY
What you can do for now is downgrade to Jersey 1.8, which should not be affected by latest changes in this area. Thanks and sorry for inconvenience!
EDIT: issue link: http://java.net/jira/browse/JERSEY-773
it is already fixed, so you should be able to use this feature in Jersey 1.10-b02 and newer.