resteasy-users — A general discussion list for the projects end users of RESTEasy.

[Resteasy-users] Test

[Alessio S. <aso...@re...>]

Testing automatic responder

Re: [Resteasy-users] Setting cookies per request in Resteasy Client

[Jim Ma <em...@re...>]

Hi Craig,
Sorry for the late response. We already moved to use jboss mailing list 
: http://resteasy.jboss.org/mailinglists. If you have any resteasy 
questions in the future, please post to the new mailing list.
To clear the cookie, did you try set a new created HttpClientClientConxt 
to the ApachHttpClientEngine and clear cookieStore  before send the 
request like below example code ?
ApacheHttpClient4Engine engine = new ApacheHttpClient4Engine();
HttpClientContext context = new HttpClientContext();
engine.setHttpContext(context);
ResteasyClient client = new 
ResteasyClientBuilder().httpEngine(engine).build();
//clear cookie
context.getCookieStore().clear();
Response response = client.target(url).request().post(entity);

Cheers,
Jim
> -------- Messaggio Inoltrato --------
> Oggetto: 	[Resteasy-users] Setting cookies per request in Resteasy Client
> Data: 	Mon, 11 Apr 2016 09:54:27 -0500
> Mittente: 	Craig Ching <cra...@gm...>
> A: 	res...@li...
>
>
>
> Hi,
>
> I’m having problems managing cookies in the Resteasy Client.  It seems like when a “Set-Cookie” is returned from a server, that there is no way to clear that cookie on a new request.  Essentially, it appears that the cookies are set on the client and not on the individual invocation (maybe via an Apache HttpContext?).  I want to take responsibility for managing cookies *completely* and do it per request.
>
> I’ve tried playing with ClientRequestFilter, but the cookies don’t show up in the headers or the cookies there.  I’m looking at what I can override in the ApacheHttpClient4Engine, but it looks like there is no way to specify a context per request.
>
> Does anyone have any ideas of other things I could try?  I’m at the point of having to drop down to Apache HttpClient directly for my calls, but I don’t want to as it’s nice using the JAX-RS Response.
>
> Thanks for any help!
>
> Cheers,
> Craig
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users

Re: [Resteasy-users] How to use JSON message body in POST

[Jim Ma <em...@re...>]

Hi,
Sorry for the so late reply. We've moved the mailing list to user jboss 
mailing list: http://resteasy.jboss.org/mailinglists from May 2016.
Did you try with add @Body annotation in TestData class and directly use 
the annotated filed in your service ? If @Body is not a required thing 
to use , can you simply try with the
latest resteasy and directly send the json request which represents the 
TestData object ? I can't see why @Body is required here.

Cheers,
Jim
> -------- Messaggio Inoltrato --------
> Oggetto: 	[Resteasy-users] How to use JSON message body in POST
> Data: 	Thu, 21 Apr 2016 11:01:20 -0400
> Mittente: 	John Sipher <jas...@gm...>
> A: 	res...@li...
>
>
>
> Hello,
>
> I'm trying to POST JSON data to a JAX-RS servlet running in WildFly 
> 8.2.0 (RESTEasy 3.0.10). I started out coding the method like this, 
> because this is what I see in every example I've found with Google 
> (this could mean I just have poor Google skills).
>
> @Path("/test")
> @Consumes("application/json;charset=utf-8")
> @Produces("application/json;charset=utf-8")
> public Response execute(TestData data) {
> AppResponse response = new AppResponse();
> // do some stuff
> return Response.status(200).entity(response).build();
> }
>
> That failed because the 
> factory.getInjectorFactory().createParameterExtractor(parameter, 
> factory) call in this constructor always returned null, which caused a 
> NullPointerException when the request was processed.
>    public MethodInjectorImpl(ResourceLocator resourceMethod, 
> ResteasyProviderFactory factory)
>    {
>       this.factory = factory;
>       this.method = resourceMethod;
> this.interfaceBasedMethod = 
> findInterfaceBasedMethod(resourceMethod.getResourceClass().getClazz(), 
> resourceMethod.getMethod());
>       params = new ValueInjector[resourceMethod.getParams().length];
>       int i = 0;
>       for (MethodParameter parameter : resourceMethod.getParams())
>       {
>          params[i] = 
> factory.getInjectorFactory().createParameterExtractor(parameter, factory);
>          if (params[i] instanceof MessageBodyParameterInjector) 
> expectsBody = true;
>          i++;
>       }
>    }
>
> That was happening because parameter.paramType is ParamType.UNKNOWN. A 
> little more debugging led me to the @Body annotation. It looks like 
> adding @Body to the parameter would fix the problem, but @Body is only 
> valid for methods and fields, not parameters. So, I changed my code to 
> this
>
> @Bodyprivate TestData data;
> @Path("/test")
> @Consumes("application/json;charset=utf-8")
> @Produces("application/json;charset=utf-8")
> public Response execute() {
> AppResponse response = new AppResponse();
> // do some stuff
> return Response.status(200).entity(response).build();
> }
>
> That "works" (my method is able to do its work and generate a 
> response), but at some point after my method finishes, RESTEasy pukes 
> and dies with this exception.
>
> 10:57:00,769 WARN  [org.jboss.resteasy.core.ExceptionHandler] (default 
> task-10) Failed executing POST /execute-ant: 
> org.jboss.resteasy.spi.InternalServerErrorException: Subresource for 
> target class has no jax-rs annotations.: 
> org.jboss.resteasy.specimpl.BuiltResponse
> at 
> org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:126) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at 
> org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:103) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at 
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at 
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at 
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at 
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at 
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) 
> [resteasy-jaxrs-3.0.10.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) 
> [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
> at 
> io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at 
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:63) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at 
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) 
> [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) 
> [undertow-core-1.1.0.Final.jar:1.1.0.Final]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
> [rt.jar:1.8.0_45]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
> [rt.jar:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
>
> Thanks in advance for any help you can offer.
>
> John

Re: [Resteasy-users] Adding Metrics to Resteasy

[Jim Ma <em...@re...>]

Hi Michael,
What kind of metrics do you need to add ? If you want to add the metrics 
to monitor the service request/response , you can
look at implement a ContainerRequestFilter or ContainerResponseFilter to 
collect the timer, counter in these places.
Or you can simply add it to the servlet filter and configure to you web 
app.
Cheers,
Jim
>
> -------- Messaggio Inoltrato --------
>
> Oggetto: 	[Resteasy-users] Adding Metrics to Resteasy
> Data: 	Fri, 2 Sep 2016 14:21:41 -0400
> Mittente: 	Mike Hills <mik...@se...>
> A: 	res...@li...
>
>
>
> I am about to look into instrumenting my resteasy calls with Metrics 
> (http://metrics.dropwizard.io/3.1.0/). Anyone have advice on which way 
> to go  - i.e interceptors , spring etc?
>
> Much appreciated.
>
> -- 
> Michael J. Hills
> Sr. CRM Architect
>
> Mobile: 603.475.5093
> Email  : mik...@se... <mailto:mik...@se...>
> Skype : mhills_sematree

[Resteasy-users] Adding Metrics to Resteasy

[Mike H. <mik...@se...>]

I am about to look into instrumenting my resteasy calls with Metrics (
http://metrics.dropwizard.io/3.1.0/). Anyone have advice on which way to go
 - i.e interceptors , spring etc?

Much appreciated.

-- 
Michael J. Hills
Sr. CRM Architect

Mobile: 603.475.5093
Email  : mik...@se...
Skype : mhills_sematree

[Resteasy-users] srinivas Gunda invited you to check out Dropbox

[Dropbox <no-...@dr...>]

Hi there,

srinivas Gunda (sri...@gm...) thinks you should use Dropbox! It’s a free and easy way to access and share your docs, photos, and videos with colleagues and friends—even if they don’t have Dropbox accounts.

Accept invite[1]

Get started through this email, and you’ll get an extra 500 MB added to your 2 GB of free space.

Happy Dropboxing!

[1]: https://www.dropbox.com/l/BcNaKOH1fYmTIVqwYIGtyh?text=1

Re: [Resteasy-users] Proper handling of NotModified/304

[Sean D. <sea...@gm...>]

Did some debugging that led me here:

https://issues.jboss.org/browse/RESTEASY-981


On Thu, Jun 9, 2016 at 4:13 PM, Sean Dawson <sea...@gm...>
wrote:

>
> (3.0.16.Final)
>
> If I use RestEasy (client) to call a RestEasy server, and that server
> throws an exception with a 304 status code (no other processing at this
> point), RestEasy on the client seems to still attempt to buffer the entity
> (in normal operation, this particular server method is supposed to return
> an InputStream and is set to @Produces("application/octet-stream")).  Since
> there's no entity, an NPE is thrown.
>
> What's the right way to do this.... ?
>
> - clear the media type
> - set the InputStream to the entity anyway before throwing exception
> - set an empty InputStream (again before throwing exception)
> - use a ClientResponseFilter to - in the case of a 304 or other error
> status - either
>      - throw an exception
>      - set the response to an empty input stream (or an error message)
>      - use abortWith to create a different response
> - not return a 304, do something else instead
>
>

[Resteasy-users] Proper handling of NotModified/304

[Sean D. <sea...@gm...>]

(3.0.16.Final)

If I use RestEasy (client) to call a RestEasy server, and that server
throws an exception with a 304 status code (no other processing at this
point), RestEasy on the client seems to still attempt to buffer the entity
(in normal operation, this particular server method is supposed to return
an InputStream and is set to @Produces("application/octet-stream")).  Since
there's no entity, an NPE is thrown.

What's the right way to do this.... ?

- clear the media type
- set the InputStream to the entity anyway before throwing exception
- set an empty InputStream (again before throwing exception)
- use a ClientResponseFilter to - in the case of a 304 or other error
status - either
     - throw an exception
     - set the response to an empty input stream (or an error message)
     - use abortWith to create a different response
- not return a 304, do something else instead

Re: [Resteasy-users] "Provider class ____ is already registered. 2nd registration is being ignored."

[John D. A. <joh...@gm...>]

I see this on the client side in 3.0.14, even though no provider is
registered.

John

On Thu, Jun 9, 2016 at 3:46 PM Sean Dawson <sea...@gm...> wrote:

>
> We're seeing this as well.
>
>
> On Thu, Jun 9, 2016 at 3:16 PM, Systema Sephiroticum <
> fal...@gm...> wrote:
>
>> I'm seeing this warning quite a bit-- I think resteasy is picking up the
>> @provider classes in various libraries and trying to register them again.
>> Once upon a time we could set resteasy.scan.providers in web.xml to tell it
>> not to scan these, but that's been deprecated...
>>
>> The warnings are probably harmless but that's a whole lotta logging every
>> time I start tomcat. Can anything be done?
>>
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports.
>> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>> _______________________________________________
>> Resteasy-users mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>>
>>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>

Re: [Resteasy-users] "Provider class ____ is already registered. 2nd registration is being ignored."

[Sean D. <sea...@gm...>]

We're seeing this as well.


On Thu, Jun 9, 2016 at 3:16 PM, Systema Sephiroticum <
fal...@gm...> wrote:

> I'm seeing this warning quite a bit-- I think resteasy is picking up the
> @provider classes in various libraries and trying to register them again.
> Once upon a time we could set resteasy.scan.providers in web.xml to tell it
> not to scan these, but that's been deprecated...
>
> The warnings are probably harmless but that's a whole lotta logging every
> time I start tomcat. Can anything be done?
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
>

[Resteasy-users] "Provider class ____ is already registered. 2nd registration is being ignored."

[Systema S. <fal...@gm...>]

I'm seeing this warning quite a bit-- I think resteasy is picking up the
@provider classes in various libraries and trying to register them again.
Once upon a time we could set resteasy.scan.providers in web.xml to tell it
not to scan these, but that's been deprecated...

The warnings are probably harmless but that's a whole lotta logging every
time I start tomcat. Can anything be done?

Re: [Resteasy-users] (no subject)

[Systema S. <fal...@gm...>]

FYI it looks like I was missing async-http-servlet-3.0-3.0.17.Final.jar
Once I added this, I was able to remove my resteasy-servlet entry from
web.xml (as the documentation recommends for servlet 3.0 containers) and
comment out the addition of my Resource class added to singletons in my
class extending Application. Looks like this approach is possible after
all!    : )

Now my concern is, given that I have other entries in web.xml for existing
servlets not being handled by RESTEasy, is there any way for RESTEasy to
handle routing only for my @Path-annotated resources? Or is it all or
nothing when it comes to having RESTEasy handle endpoints? I could set
@ApplicationPath("") in my application, but then it intercepts everything.
I'd prefer that it only intercepted paths for which it has resources, so
that I can gradually move existing endpoints into resteasy without having
to prefix them with "/rest" or something as I do so.

I know I can explicitly list out all my resources with the
resteasy.resources context-param in web.xml, but this seems like a step
backwards.

On Mon, Jun 6, 2016 at 9:33 AM, Sean Dawson <sea...@gm...>
wrote:

>
> Hi again,
>
> I'm currently maintaining some RestEasy code that includes both newer and
> legacy ways of setting things up - and I'm no completely clear on what the
> latest and greatest way of doing everything RestEasy is at this point.  I'm
> working my way there but obviously as most of us, have to balance competing
> priorities.
>
> So unfortunately I can't give you a really good answer now.  I would read
> the docs and try to separate the old way of doing things with the
> new/current recommended.  Also maybe look at the most recent RestEasy
> examples you can find in the code base.
>

Re: [Resteasy-users] (no subject)

[Sean D. <sea...@gm...>]

Hi again,

I'm currently maintaining some RestEasy code that includes both newer and
legacy ways of setting things up - and I'm no completely clear on what the
latest and greatest way of doing everything RestEasy is at this point.  I'm
working my way there but obviously as most of us, have to balance competing
priorities.

So unfortunately I can't give you a really good answer now.  I would read
the docs and try to separate the old way of doing things with the
new/current recommended.  Also maybe look at the most recent RestEasy
examples you can find in the code base.


On Fri, Jun 3, 2016 at 7:10 PM, Systema Sephiroticum <
fal...@gm...> wrote:

> Also, sorry for the double-email, but I noticed one other thing. the
> JSR311 spec recommends:
>
> "If not using the Servlet 3 framework pluggability mechanism (e.g. in a
> pre-Servet 3.0 container), the servlet-class orfilter-class element of the
>  web.xml descriptor SHOULD name the JAX-RS implementation-supplied
> servlet or filter class respectively. The Application subclass SHOULD be
> identified using an init-param with a param-name ofjavax.ws.rs.Application
> ."
>
> I'm a bit confused at this because, although I *am* using a servlet 3.0
> container (Tomcat 7.0.59), your example that works still utilizes the
> init-param with java.ws.rs.Application. Is this only necessary because I
> don't have Maven, and can't add a dependency as mentioned here?
>
>
> http://docs.jboss.org/resteasy/docs/3.0.17.Final/userguide/html_single/index.html#d4e113
>
> Or is resteasy doing something a little different than the JAX-RS spec's
> recommendation, instead requiring this init-param?
>
> Thanks again
>
>
> On Fri, Jun 3, 2016 at 2:45 PM, Systema Sephiroticum <
> fal...@gm...> wrote:
>
>> Hi Sean,
>>
>> Thank you for your swift reply. That sample program does indeed work with
>> my tomcat. The magic line is " singletons.add(new HelloWorld()); ", however
>> I'm wondering if it is possible to have RESTeasy automatically scan for
>> these resources. According to the resteasy docs, "If you return any empty
>> set for by classes and singletons [in your Application], your WAR will be
>> scanned for JAX-RS annotation resource and provider classes." But this
>> doesn't seem to happen when I return null or an empty set from
>> getSingletons(). There was a resteasy.scan web.xml property, however
>> apparently it has been deprecated, and resteasy is supposed to scan for
>> these resources itself. This is the behavior that I am hoping for. I'm
>> using an exploded-war deployment locally for my application, which I hope
>> does not preclude me from taking advantage of this functionality.
>>
>> Fortunately, I got my logging working. The warning when I attempt to use
>> the old resteasy.scan is "resteasy.scan is no longer supported. Use a
>> servlet 3.0 container and the ResteasyServletInitializer". This seems like
>> a stab in the right direction, but I'm not sure what to do with
>> ResteasyServletInitializer.
>>
>> Again, very appreciative of your response.
>>
>> On Fri, Jun 3, 2016 at 9:36 AM, Sean Dawson <sea...@gm...>
>> wrote:
>>
>>>
>>> You should definitely read through all the documentation here:
>>>
>>>
>>> http://docs.jboss.org/resteasy/docs/3.0.17.Final/userguide/html_single/index.html
>>>
>>> And take a look at the examples.
>>>
>>> This is a bit of an old way of doing things, but based on what you have,
>>> and the info here:
>>>
>>> http://www.mkyong.com/webservices/jax-rs/resteasy-hello-world-example/
>>>
>>> I got your example working.  I did use maven (dependencies on RestEasy
>>> and Jetty).  But here are the files:
>>>
>>> import java.util.HashSet;
>>> import java.util.Set;
>>> import javax.ws.rs.ApplicationPath;
>>> import javax.ws.rs.core.Application;
>>>
>>> @ApplicationPath("/rest")
>>> public class RootApplication extends Application
>>> {
>>>     private Set<Object> singletons = new HashSet<Object>();
>>>
>>>     public RootApplication()
>>>     {
>>>         singletons.add(new HelloWorld());
>>>     }
>>>
>>>     @Override
>>>     public Set<Object> getSingletons()
>>>     {
>>>         return singletons;
>>>     }
>>> }
>>>
>>>
>>> import java.util.Date;
>>> import javax.ws.rs.GET;
>>> import javax.ws.rs.Path;
>>> import javax.ws.rs.Produces;
>>>
>>> @Path("hello")
>>> public class HelloWorld
>>> {
>>>     @GET
>>>     @Produces("text/plain")
>>>     public String helloResource()
>>>     {
>>>         return "Hello! It's " + new Date();
>>>     }
>>> }
>>>
>>>
>>> import java.io.File;
>>> import org.eclipse.jetty.server.Server;
>>> import org.eclipse.jetty.webapp.WebAppContext;
>>>
>>> public class ReTest
>>> {
>>>     public static void main(String[] args) throws Exception
>>>     {
>>>         WebAppContext context = new WebAppContext();
>>>         context.setDescriptor(new File("resteasytest/src/main/webapp/WEB-INF/web.xml").getAbsolutePath());
>>>         context.setResourceBase(new File("resteasytest/src/main/webapp").getAbsolutePath());
>>>         context.setContextPath("/");
>>>         Server server = new Server(8123);
>>>         server.setHandler(context);
>>>         server.start();
>>>     }
>>> }
>>>
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
>>>          version="3.0">
>>>
>>>     <servlet>
>>>         <servlet-name>resteasy-servlet</servlet-name>
>>>         <servlet-class>
>>>             org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
>>>         </servlet-class>
>>>         <init-param>
>>>             <param-name>javax.ws.rs.Application</param-name>
>>>             <param-value>RootApplication</param-value>
>>>         </init-param>
>>>     </servlet>
>>>
>>>     <servlet-mapping>
>>>         <servlet-name>resteasy-servlet</servlet-name>
>>>         <url-pattern>/*</url-pattern>
>>>     </servlet-mapping>
>>>
>>> </web-app>
>>>
>>>
>>> Running ReTest and going to:
>>> http://localhost:8123/hello
>>>
>>>
>>> Resulted in:
>>>
>>> Hello! It's Fri Jun 03 12:30:47 EDT 2016
>>>
>>>
>>>
>>> On Thu, Jun 2, 2016 at 11:01 PM, Systema Sephiroticum <
>>> fal...@gm...> wrote:
>>>
>>>>    I've been trying for a few days now to obtain a response with
>>>> RESTeasy,
>>>>     only with very little success--I was able to receive a request on my
>>>>     Resource class when explicitly adding said resource class as a
>>>> singleton in
>>>>     my Application-extending class, but I've had no luck in trying to
>>>> make
>>>>     RESTeasy scan for these classes automatically, even with
>>>> resteasy.scan set
>>>>     to true in web.xml
>>>>
>>>>     My web.xml file is empty except for a resteasy.logger.type
>>>> context-param
>>>>     specifying LOG4J.
>>>>
>>>>     Here's a basic application class (apologies for lack of formatting,
>>>> seems like any font change leads to my email getting bounced):
>>>>
>>>>
>>>>
>>>>     import javax.ws.rs.ApplicationPath;
>>>>     import javax.ws.rs.core.Application;
>>>>     @ApplicationPath("/rest")
>>>>     public class RootApplication extends Application {
>>>>     }
>>>>
>>>>
>>>>     And here's a basic resource class:
>>>>
>>>>
>>>>
>>>>     import java.util.Date;
>>>>     import javax.ws.rs.GET;
>>>>     import javax.ws.rs.Path;
>>>>     import javax.ws.rs.Produces;
>>>>
>>>>     @Path("/hello")
>>>>     public class HelloWorld {
>>>>        @GET
>>>>        @Produces("text/plain")
>>>>        public String helloResource() {
>>>>           return "Hello! It's "+new Date();
>>>>        }
>>>>     }
>>>>
>>>>
>>>>
>>>>
>>>>     I don't use Maven, so I have no pom.xml, though to my knowledge
>>>> this isn't
>>>>     relevant if I just grab the needed jars myself. These are the jars
>>>> I've
>>>>     added:
>>>>
>>>>     httpclient-4.3.jar
>>>>     annotations.jar
>>>>     jars-api-3.0.9.Final.jar
>>>>     resteasy-jaxrs-3.0.17.Final.jar
>>>>
>>>>     I feel as though this would be easier to diagnose if restEASY logged
>>>>     anything, however it's not doing so despite having this property in
>>>> my
>>>>     log4j.properties:
>>>>
>>>>     log4j.logger.org.jboss.resteasy=INFO
>>>>
>>>>
>>>>     Visiting http://localhost/rest/hello  after all this just returns
>>>> a basic
>>>>     Tomcat 404 page, "The requested resource is not available". I
>>>> really have
>>>>     no idea what's going on under the hood with logging not working. My
>>>> tomcat
>>>>     is functioning otherwise, also.
>>>>
>>>>     Any help would be greatly appreciated.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>>> traffic
>>>> patterns at an interface-level. Reveals which users, apps, and
>>>> protocols are
>>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>>> planning reports.
>>>> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>>>> _______________________________________________
>>>> Resteasy-users mailing list
>>>> Res...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>>>>
>>>>
>>>
>>
>

Re: [Resteasy-users] (no subject)

[Systema S. <fal...@gm...>]

Hi Sean,

Thank you for your swift reply. That sample program does indeed work with
my tomcat. The magic line is " singletons.add(new HelloWorld()); ", however
I'm wondering if it is possible to have RESTeasy automatically scan for
these resources. According to the resteasy docs, "If you return any empty
set for by classes and singletons [in your Application], your WAR will be
scanned for JAX-RS annotation resource and provider classes." But this
doesn't seem to happen when I return null or an empty set from
getSingletons(). There was a resteasy.scan web.xml property, however
apparently it has been deprecated, and resteasy is supposed to scan for
these resources itself. This is the behavior that I am hoping for. I'm
using an exploded-war deployment locally for my application, which I hope
does not preclude me from taking advantage of this functionality.

Fortunately, I got my logging working. The warning when I attempt to use
the old resteasy.scan is "resteasy.scan is no longer supported. Use a
servlet 3.0 container and the ResteasyServletInitializer". This seems like
a stab in the right direction, but I'm not sure what to do with
ResteasyServletInitializer.

Again, very appreciative of your response.

On Fri, Jun 3, 2016 at 9:36 AM, Sean Dawson <sea...@gm...>
wrote:

>
> You should definitely read through all the documentation here:
>
>
> http://docs.jboss.org/resteasy/docs/3.0.17.Final/userguide/html_single/index.html
>
> And take a look at the examples.
>
> This is a bit of an old way of doing things, but based on what you have,
> and the info here:
>
> http://www.mkyong.com/webservices/jax-rs/resteasy-hello-world-example/
>
> I got your example working.  I did use maven (dependencies on RestEasy and
> Jetty).  But here are the files:
>
> import java.util.HashSet;
> import java.util.Set;
> import javax.ws.rs.ApplicationPath;
> import javax.ws.rs.core.Application;
>
> @ApplicationPath("/rest")
> public class RootApplication extends Application
> {
>     private Set<Object> singletons = new HashSet<Object>();
>
>     public RootApplication()
>     {
>         singletons.add(new HelloWorld());
>     }
>
>     @Override
>     public Set<Object> getSingletons()
>     {
>         return singletons;
>     }
> }
>
>
> import java.util.Date;
> import javax.ws.rs.GET;
> import javax.ws.rs.Path;
> import javax.ws.rs.Produces;
>
> @Path("hello")
> public class HelloWorld
> {
>     @GET
>     @Produces("text/plain")
>     public String helloResource()
>     {
>         return "Hello! It's " + new Date();
>     }
> }
>
>
> import java.io.File;
> import org.eclipse.jetty.server.Server;
> import org.eclipse.jetty.webapp.WebAppContext;
>
> public class ReTest
> {
>     public static void main(String[] args) throws Exception
>     {
>         WebAppContext context = new WebAppContext();
>         context.setDescriptor(new File("resteasytest/src/main/webapp/WEB-INF/web.xml").getAbsolutePath());
>         context.setResourceBase(new File("resteasytest/src/main/webapp").getAbsolutePath());
>         context.setContextPath("/");
>         Server server = new Server(8123);
>         server.setHandler(context);
>         server.start();
>     }
> }
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
>          version="3.0">
>
>     <servlet>
>         <servlet-name>resteasy-servlet</servlet-name>
>         <servlet-class>
>             org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
>         </servlet-class>
>         <init-param>
>             <param-name>javax.ws.rs.Application</param-name>
>             <param-value>RootApplication</param-value>
>         </init-param>
>     </servlet>
>
>     <servlet-mapping>
>         <servlet-name>resteasy-servlet</servlet-name>
>         <url-pattern>/*</url-pattern>
>     </servlet-mapping>
>
> </web-app>
>
>
> Running ReTest and going to:
> http://localhost:8123/hello
>
>
> Resulted in:
>
> Hello! It's Fri Jun 03 12:30:47 EDT 2016
>
>
>
> On Thu, Jun 2, 2016 at 11:01 PM, Systema Sephiroticum <
> fal...@gm...> wrote:
>
>>    I've been trying for a few days now to obtain a response with RESTeasy,
>>     only with very little success--I was able to receive a request on my
>>     Resource class when explicitly adding said resource class as a
>> singleton in
>>     my Application-extending class, but I've had no luck in trying to make
>>     RESTeasy scan for these classes automatically, even with
>> resteasy.scan set
>>     to true in web.xml
>>
>>     My web.xml file is empty except for a resteasy.logger.type
>> context-param
>>     specifying LOG4J.
>>
>>     Here's a basic application class (apologies for lack of formatting,
>> seems like any font change leads to my email getting bounced):
>>
>>
>>
>>     import javax.ws.rs.ApplicationPath;
>>     import javax.ws.rs.core.Application;
>>     @ApplicationPath("/rest")
>>     public class RootApplication extends Application {
>>     }
>>
>>
>>     And here's a basic resource class:
>>
>>
>>
>>     import java.util.Date;
>>     import javax.ws.rs.GET;
>>     import javax.ws.rs.Path;
>>     import javax.ws.rs.Produces;
>>
>>     @Path("/hello")
>>     public class HelloWorld {
>>        @GET
>>        @Produces("text/plain")
>>        public String helloResource() {
>>           return "Hello! It's "+new Date();
>>        }
>>     }
>>
>>
>>
>>
>>     I don't use Maven, so I have no pom.xml, though to my knowledge this
>> isn't
>>     relevant if I just grab the needed jars myself. These are the jars
>> I've
>>     added:
>>
>>     httpclient-4.3.jar
>>     annotations.jar
>>     jars-api-3.0.9.Final.jar
>>     resteasy-jaxrs-3.0.17.Final.jar
>>
>>     I feel as though this would be easier to diagnose if restEASY logged
>>     anything, however it's not doing so despite having this property in my
>>     log4j.properties:
>>
>>     log4j.logger.org.jboss.resteasy=INFO
>>
>>
>>     Visiting http://localhost/rest/hello  after all this just returns a
>> basic
>>     Tomcat 404 page, "The requested resource is not available". I really
>> have
>>     no idea what's going on under the hood with logging not working. My
>> tomcat
>>     is functioning otherwise, also.
>>
>>     Any help would be greatly appreciated.
>>
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports.
>> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>> _______________________________________________
>> Resteasy-users mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>>
>>
>

Re: [Resteasy-users] (no subject)

[Sean D. <sea...@gm...>]

You should definitely read through all the documentation here:

http://docs.jboss.org/resteasy/docs/3.0.17.Final/userguide/html_single/index.html

And take a look at the examples.

This is a bit of an old way of doing things, but based on what you have,
and the info here:

http://www.mkyong.com/webservices/jax-rs/resteasy-hello-world-example/

I got your example working.  I did use maven (dependencies on RestEasy and
Jetty).  But here are the files:

import java.util.HashSet;
import java.util.Set;
import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;

@ApplicationPath("/rest")
public class RootApplication extends Application
{
    private Set<Object> singletons = new HashSet<Object>();

    public RootApplication()
    {
        singletons.add(new HelloWorld());
    }

    @Override
    public Set<Object> getSingletons()
    {
        return singletons;
    }
}


import java.util.Date;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.Produces;

@Path("hello")
public class HelloWorld
{
    @GET
    @Produces("text/plain")
    public String helloResource()
    {
        return "Hello! It's " + new Date();
    }
}


import java.io.File;
import org.eclipse.jetty.server.Server;
import org.eclipse.jetty.webapp.WebAppContext;

public class ReTest
{
    public static void main(String[] args) throws Exception
    {
        WebAppContext context = new WebAppContext();
        context.setDescriptor(new
File("resteasytest/src/main/webapp/WEB-INF/web.xml").getAbsolutePath());
        context.setResourceBase(new
File("resteasytest/src/main/webapp").getAbsolutePath());
        context.setContextPath("/");
        Server server = new Server(8123);
        server.setHandler(context);
        server.start();
    }
}


<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
         version="3.0">

    <servlet>
        <servlet-name>resteasy-servlet</servlet-name>
        <servlet-class>
            org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher
        </servlet-class>
        <init-param>
            <param-name>javax.ws.rs.Application</param-name>
            <param-value>RootApplication</param-value>
        </init-param>
    </servlet>

    <servlet-mapping>
        <servlet-name>resteasy-servlet</servlet-name>
        <url-pattern>/*</url-pattern>
    </servlet-mapping>

</web-app>


Running ReTest and going to:
http://localhost:8123/hello


Resulted in:

Hello! It's Fri Jun 03 12:30:47 EDT 2016



On Thu, Jun 2, 2016 at 11:01 PM, Systema Sephiroticum <
fal...@gm...> wrote:

>    I've been trying for a few days now to obtain a response with RESTeasy,
>     only with very little success--I was able to receive a request on my
>     Resource class when explicitly adding said resource class as a
> singleton in
>     my Application-extending class, but I've had no luck in trying to make
>     RESTeasy scan for these classes automatically, even with resteasy.scan
> set
>     to true in web.xml
>
>     My web.xml file is empty except for a resteasy.logger.type
> context-param
>     specifying LOG4J.
>
>     Here's a basic application class (apologies for lack of formatting,
> seems like any font change leads to my email getting bounced):
>
>
>
>     import javax.ws.rs.ApplicationPath;
>     import javax.ws.rs.core.Application;
>     @ApplicationPath("/rest")
>     public class RootApplication extends Application {
>     }
>
>
>     And here's a basic resource class:
>
>
>
>     import java.util.Date;
>     import javax.ws.rs.GET;
>     import javax.ws.rs.Path;
>     import javax.ws.rs.Produces;
>
>     @Path("/hello")
>     public class HelloWorld {
>        @GET
>        @Produces("text/plain")
>        public String helloResource() {
>           return "Hello! It's "+new Date();
>        }
>     }
>
>
>
>
>     I don't use Maven, so I have no pom.xml, though to my knowledge this
> isn't
>     relevant if I just grab the needed jars myself. These are the jars I've
>     added:
>
>     httpclient-4.3.jar
>     annotations.jar
>     jars-api-3.0.9.Final.jar
>     resteasy-jaxrs-3.0.17.Final.jar
>
>     I feel as though this would be easier to diagnose if restEASY logged
>     anything, however it's not doing so despite having this property in my
>     log4j.properties:
>
>     log4j.logger.org.jboss.resteasy=INFO
>
>
>     Visiting http://localhost/rest/hello  after all this just returns a
> basic
>     Tomcat 404 page, "The requested resource is not available". I really
> have
>     no idea what's going on under the hood with logging not working. My
> tomcat
>     is functioning otherwise, also.
>
>     Any help would be greatly appreciated.
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
>

[Resteasy-users] (no subject)

[Systema S. <fal...@gm...>]

   I've been trying for a few days now to obtain a response with RESTeasy,
    only with very little success--I was able to receive a request on my
    Resource class when explicitly adding said resource class as a
singleton in
    my Application-extending class, but I've had no luck in trying to make
    RESTeasy scan for these classes automatically, even with resteasy.scan
set
    to true in web.xml

    My web.xml file is empty except for a resteasy.logger.type context-param
    specifying LOG4J.

    Here's a basic application class (apologies for lack of formatting,
seems like any font change leads to my email getting bounced):



    import javax.ws.rs.ApplicationPath;
    import javax.ws.rs.core.Application;
    @ApplicationPath("/rest")
    public class RootApplication extends Application {
    }


    And here's a basic resource class:



    import java.util.Date;
    import javax.ws.rs.GET;
    import javax.ws.rs.Path;
    import javax.ws.rs.Produces;

    @Path("/hello")
    public class HelloWorld {
       @GET
       @Produces("text/plain")
       public String helloResource() {
          return "Hello! It's "+new Date();
       }
    }




    I don't use Maven, so I have no pom.xml, though to my knowledge this
isn't
    relevant if I just grab the needed jars myself. These are the jars I've
    added:

    httpclient-4.3.jar
    annotations.jar
    jars-api-3.0.9.Final.jar
    resteasy-jaxrs-3.0.17.Final.jar

    I feel as though this would be easier to diagnose if restEASY logged
    anything, however it's not doing so despite having this property in my
    log4j.properties:

    log4j.logger.org.jboss.resteasy=INFO


    Visiting http://localhost/rest/hello  after all this just returns a
basic
    Tomcat 404 page, "The requested resource is not available". I really
have
    no idea what's going on under the hood with logging not working. My
tomcat
    is functioning otherwise, also.

    Any help would be greatly appreciated.

Re: [Resteasy-users] Setting cookies per request in Resteasy Client

[Weinan Li <we...@re...>]

Hi Craig,

We depreated this mailing list, please start to use the new ones:

https://lists.jboss.org/mailman/listinfo/resteasy-dev
https://lists.jboss.org/mailman/listinfo/resteasy
https://lists.jboss.org/mailman/listinfo/resteasy-commits

--
Weinan Li / JBoss



> On Apr 11, 2016, at 10:54 PM, Craig Ching <cra...@gm...> wrote:
> 
> Hi,
> 
> I’m having problems managing cookies in the Resteasy Client.  It seems like when a “Set-Cookie” is returned from a server, that there is no way to clear that cookie on a new request.  Essentially, it appears that the cookies are set on the client and not on the individual invocation (maybe via an Apache HttpContext?).  I want to take responsibility for managing cookies *completely* and do it per request.
> 
> I’ve tried playing with ClientRequestFilter, but the cookies don’t show up in the headers or the cookies there.  I’m looking at what I can override in the ApacheHttpClient4Engine, but it looks like there is no way to specify a context per request.
> 
> Does anyone have any ideas of other things I could try?  I’m at the point of having to drop down to Apache HttpClient directly for my calls, but I don’t want to as it’s nice using the JAX-RS Response.
> 
> Thanks for any help!
> 
> Cheers,
> Craig
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users

[Resteasy-users] the mailing-list on sourceforge has been deprecated

[Weinan Li <we...@re...>]

Hi,

We start to use the new mailing lists:

- https://lists.jboss.org/mailman/listinfo/resteasy-dev (Which discusses development issues)
- https://lists.jboss.org/mailman/listinfo/resteasy (Which discusses general usage issues)
- https://lists.jboss.org/mailman/listinfo/resteasy-commits (Which is hooked to github repo so that commit messages are now automatically sent to the list)

--
Weinan Li / JBoss

[Resteasy-users] How to use JSON message body in POST

[John S. <jas...@gm...>]

Hello,

I'm trying to POST JSON data to a JAX-RS servlet running in WildFly 8.2.0
(RESTEasy 3.0.10). I started out coding the method like this, because this
is what I see in every example I've found with Google (this could mean I
just have poor Google skills).

@Path("/test")
@Consumes("application/json;charset=utf-8")
@Produces("application/json;charset=utf-8")
public Response execute(TestData data) {
AppResponse response = new AppResponse();
// do some stuff
return Response.status(200).entity(response).build();
}

That failed because the
factory.getInjectorFactory().createParameterExtractor(parameter,
factory) call in this constructor always returned null, which caused a
NullPointerException when the request was processed.
   public MethodInjectorImpl(ResourceLocator resourceMethod,
ResteasyProviderFactory factory)
   {
      this.factory = factory;
      this.method = resourceMethod;
      this.interfaceBasedMethod =
findInterfaceBasedMethod(resourceMethod.getResourceClass().getClazz(),
resourceMethod.getMethod());
      params = new ValueInjector[resourceMethod.getParams().length];
      int i = 0;
      for (MethodParameter parameter : resourceMethod.getParams())
      {
         params[i] =
factory.getInjectorFactory().createParameterExtractor(parameter, factory);
         if (params[i] instanceof MessageBodyParameterInjector) expectsBody
= true;
         i++;
      }
   }

That was happening because parameter.paramType is ParamType.UNKNOWN. A
little more debugging led me to the @Body annotation. It looks like adding
@Body to the parameter would fix the problem, but @Body is only valid for
methods and fields, not parameters. So, I changed my code to this

@Body private TestData data;
@Path("/test")
@Consumes("application/json;charset=utf-8")
@Produces("application/json;charset=utf-8")
public Response execute() {
AppResponse response = new AppResponse();
// do some stuff
return Response.status(200).entity(response).build();
}

That "works" (my method is able to do its work and generate a response),
but at some point after my method finishes, RESTEasy pukes and dies with
this exception.

10:57:00,769 WARN  [org.jboss.resteasy.core.ExceptionHandler] (default
task-10) Failed executing POST /execute-ant:
org.jboss.resteasy.spi.InternalServerErrorException: Subresource for target
class has no jax-rs annotations.: org.jboss.resteasy.specimpl.BuiltResponse
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:126)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:103)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
[resteasy-jaxrs-3.0.10.Final.jar:]
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
[resteasy-jaxrs-3.0.10.Final.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at
io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:63)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166)
[undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759)
[undertow-core-1.1.0.Final.jar:1.1.0.Final]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[rt.jar:1.8.0_45]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[rt.jar:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]

Thanks in advance for any help you can offer.

John

[Resteasy-users] Setting cookies per request in Resteasy Client

[Craig C. <cra...@gm...>]

Hi,

I’m having problems managing cookies in the Resteasy Client.  It seems like when a “Set-Cookie” is returned from a server, that there is no way to clear that cookie on a new request.  Essentially, it appears that the cookies are set on the client and not on the individual invocation (maybe via an Apache HttpContext?).  I want to take responsibility for managing cookies *completely* and do it per request.

I’ve tried playing with ClientRequestFilter, but the cookies don’t show up in the headers or the cookies there.  I’m looking at what I can override in the ApacheHttpClient4Engine, but it looks like there is no way to specify a context per request.

Does anyone have any ideas of other things I could try?  I’m at the point of having to drop down to Apache HttpClient directly for my calls, but I don’t want to as it’s nice using the JAX-RS Response.

Thanks for any help!

Cheers,
Craig

[Resteasy-users] How to configure JAX-RS 2.0 client to ignore cookies?

[Steffens, M. <Mic...@ve...>]

Hello,

how can I configure the RESTEasy JAX-RS 2.0 javax.ws.rs.client.Client to ignore cookies? The closest hint I found is

  https://docs.jboss.org/resteasy/docs/3.0.14.Final/userguide/html/RESTEasy_Client_Framework.html#d4e2141

which refers to "Configuration also lets you set various configuration properties that may be needed", but does not elaborate on available properties or possible values.

Best regards

Michael Steffens
--------------------------------------------------------
Cloud Software Architect, CISSP
RDI4

Vector Informatik GmbH
Ingersheimer Str. 24
70499 Stuttgart
Germany
Tel.: +49 711 80670-2139
Fax: +49 711 80670-
mailto: Mic...@ve...<mailto:Mic...@ve...>
Internet: www.vector.com<http://www.vector.com>

Head Office: Stuttgart
Commercial Register: Amtsgericht Stuttgart, HRB 17317
Managing Directors:
Dr. Thomas Beck, Thomas Riegraf
--------------------------------------------------------

Re: [Resteasy-users] Help needed for data validation in XML REST request in case of Bigdecimal

[Weinan Li <we...@re...>]

Hi Shyama,

The 2.3.2 is too old. And bean validation is fully rewritten in 3.x.

--
Weinan Li / JBoss



> On Mar 29, 2016, at 10:49 PM, shyama ks <shy...@gm...> wrote:
> 
> Hi Team,
> 
> 
> In REST API implementation with Bean validation enabled, in case we send a garbage value for BigDecimal data type, same is converted into a null value in JAXB class.
> For our application we need to throw error in case of garbage value scenario, but no error to be thrown in case the value is not provided. But default behavior of resteasy for garbage value and for no value, JAXB class hold the null value for that element.
> Is there any way in which we can differentiate these two scenario and throw error accordingly.
> 
> resteasy version: 2.3.2
> We are using JBOSS EAP 6.1 as application server
> 
> -- 
> Thanks,
> Shyama Sharma,
> 
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140_______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users

[Resteasy-users] Help needed for data validation in XML REST request in case of Bigdecimal

[shyama ks <shy...@gm...>]

Hi Team,


In REST API implementation with Bean validation enabled, in case we send a
garbage value for BigDecimal data type, same is converted into a null value
in JAXB class.
For our application we need to throw error in case of garbage value
scenario, but no error to be thrown in case the value is not provided. But
default behavior of resteasy for garbage value and for no value, JAXB class
hold the null value for that element.
Is there any way in which we can differentiate these two scenario and throw
error accordingly.

resteasy version: 2.3.2
We are using JBOSS EAP 6.1 as application server

-- 
Thanks,
Shyama Sharma,

Re: [Resteasy-users] Eventhandler registration for JAXB while unmarhsalling in Resteasy

[Savvas A. M. <sav...@gm...>]

Hi Kaushal,

If I am understanding your requirement right then you probably want to look
into ReaderInterceptor(s) and implement one of those. You should  be able
to register them with @Provider.

HTH,
Savvas
On 17 Mar 2016 16:11, "Kaushal Kishore Agrawal" <kau...@gm...>
wrote:

> Hi All,
>
> Is there any way in which I can register custom event handler in resteasy
> for JAXB unmarshalling. Can it be done in a declarative way, like the way
> we use to add providers
>
> I need the same to register a custom ValidationEventHandler
>
> Thanks,
> Kaushal Kishore
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
>

[Resteasy-users] Eventhandler registration for JAXB while unmarhsalling in Resteasy

[Kaushal K. A. <kau...@gm...>]

Hi All,

Is there any way in which I can register custom event handler in resteasy
for JAXB unmarshalling. Can it be done in a declarative way, like the way
we use to add providers

I need the same to register a custom ValidationEventHandler

Thanks,
Kaushal Kishore