I would like to make a web API that can return JSON data but I'm debating
whether to make it RESTful or whether to try something more along the lines of
an orchestration API.
Can resteasy make an API that responds with multiple data types in one response?
Does resteasy have the ability to do dee
Thanks, i'll fix it tomorrow when I do a 3.0.8 release.
On 4/7/2014 9:32 PM, John D. Ament wrote:
> Hi
>
> Just noticed that in master right now, the code can't compile. There's
> a new resteasy-hibernatevalidator-provider module that depends on the
> resteasy-cdi module, however the resteasy-cd
Hi
Just noticed that in master right now, the code can't compile. There's a
new resteasy-hibernatevalidator-provider module that depends on the
resteasy-cdi module, however the resteasy-cdi module doesn't come until
much later in the build.
Likewise, Resteasy CDI doesn't compile because of:
[E
I think it'd be useful. :)
On Mon, Apr 7, 2014 at 8:31 PM, Scott Stark wrote:
> I wouldn't worry about it unless its useful in general as I would rather
> just use what is shipped with the wildfly distribution to simplify set in
> the lab. Like I said, it is a simple workaround to wrap the clie
I wouldn't worry about it unless its useful in general as I would rather just
use what is shipped with the wildfly distribution to simplify set in the lab.
Like I said, it is a simple workaround to wrap the client proxy in another
proxy that just overrides this method to build the request uri wi
No, there's no workaround at the moment. If you are able to upgrade to
latest/greatest of Resteasy, I could add something in the 3.0.8 release
that is tomorrow.
On 4/7/2014 7:32 PM, Scott Stark wrote:
>
> I have a client interface with a method like:
>
> public interface INSP {
> @PUT
>
I have a client interface with a method like:
public interface INSP {
@PUT
@Path("/{domain}/subscriptions/{endpoint}{resourcePath}")
@Produces("application/json")
public String subscribeEndpointResource(@PathParam("domain") String domain,
@PathParam("endpoint") Str
Are you saying this is preferable to pivoting on custom media-types? I
don't care for the versioned-URI scheme because it puts the same
resource at multiple URIs and thus the I's are no longer U...
On 04/06/2014 08:58 AM, Bill Burke wrote:
> Resteasy cannot dispatch based on header, but I don't
