Yeah, I've run into this too (my situation is worse, I have RESTeasy
w/ Jackson, Apache CXF w/ Jettison and a third system using Spring MVC
w/ Jackson).
Jettison's JSON structure is more like XML with its use of root
elements in a parent wrapper tag. This is acceptable by JSON
standards, but not
Bill,
From the looks of it, the framework is actually leveraging your client
framework..
https://github.com/arquillian/arquillian-extension-rest/blob/master/rest-client/impl/impl-3x/src/main/java/org/jboss/arquillian/extension/rest/client/RestEnricher.java#L94
Anyways, the use cases are many.
I assumed this would happen, based on Bill's email. you'll probably
need to extend the CdiInjectorFactory to use your own BeanManager.
On Tue, Nov 26, 2013 at 1:58 PM, Christian Helmbold
christian.helmb...@yahoo.de wrote:
Thank you. After adding one more dependency (javax.servlet-api), I get
in an SE environment.
John
On Tue, Nov 26, 2013 at 6:06 PM, Bill Burke bbu...@redhat.com wrote:
On 11/26/2013 4:17 PM, Christian Helmbold wrote:
John D. Ament john.d.am...@gmail.com schrieb am 20:23 Dienstag,
26.November 2013:
I assumed this would happen, based on Bill's email.
You're
Hi all,
Wanted to get your opinions. What is the right time to use @Encoded?
Purely from a security scan standpoint, a number of places in my
coded were picked up for XSS, and I'm wondering if annotating these
endpoints with @Encoded would help.
John
integration with cdi, I could be inadvertently
causing multiple initializations.
Thanks for the response. I posted a similar question to weld after you
implicitly confirmed my code is not at fault.
John
On Fri, Dec 20, 2013 at 6:50 PM, John D. Ament john.d.am...@gmail.com
wrote:
Hey John
Hi all,
In case anyone's interested, I just put out a blog post on how you can
use RestEasy and the Netty Embedded Server with Weld.
http://john-ament.blogspot.com/2014/01/bridging-netty-resteasy-and-weld.html
and if you'd like to see the code:
https://github.com/johnament/resteasy-netty-cdi
Hi all,
Just wondering if there are any pointers to how to best handle a file
upload via RestEasy's NettyJaxrsServer? When I was doing it via an
app server, it was easy because there was an HTTP request. Would
injecting @Context HttpServletRequest still work here? I'm inclined
to think not but
) {
inputPart.setMediaType(MediaType.APPLICATION_JSON_TYPE);
MyClass rep = inputPart.getBody(new GenericTypeMyClass(){});
}
return Response.noContent().build();
}
On 2/16/2014 1:17 PM, John D. Ament wrote:
Hi all,
Just wondering if there are any pointers
Friso,
TO an extent, yes this would compete with DropWizard, but leverage
some EE technology in the mix (CDI).
John
On Fri, Feb 21, 2014 at 9:14 AM, Friso Vrolijken
friso.vrolij...@caci.nl wrote:
Hi,
-Oorspronkelijk bericht-
Great stuff, but still don't understand why you guys want
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:
Hmmm ok weird one.
I had a missing classpath dependency. However, even with that fixed no
luck.
I took a copy of ResteasyJackson2Provider and changed the produces/consumes
to be application/json instead of application/*+json and it worked fine.
John
On Mon Jan 26 2015 at 12:37:22 PM John D
Hi,
I'm using a simple SE client w/ RestEasy to talk to multiple systems.
One system exposes its APIs using Jackson1 annotations and the other uses
Jackson2 annotations.
I create two distinct clients for each of them, one registering the jackson
provider and the other registering the jackson2
Hi Jakub!
I think you're looking for ContainerResponseFilter.
John
On Fri, Feb 27, 2015 at 8:03 AM Jakub Narloch jmnarl...@gmail.com wrote:
So,
After a quick research I am trying to find the counterpart
of ClientErrorInterceptor for RESTEasy 3.x, any sugestions?
Regards,
Jakub Narloch
Hi all,
I was playing with the YAML provider today and saw an issue. In the local
unit tests, everything runs fine. However when you deploy the equivalent
example to the app server it was failing. I believe its a class loader
issue, since they seem to use some basic class loading support to do
HI Dave,
You have a context param which is disabling scanning
resteasy.resources
zedi.pacbridge.web.services.OutgoingRequests,
zedi.pacbridge.web.services.Connections
Please add your class here, or stop using the context param.
On
16 matches
Mail list logo