Menu
▾
▴
resteasy-users — A general discussion list for the projects end users of RESTEasy.
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2010 |
Jan
(1) |
Feb
(2) |
Mar
(6) |
Apr
(5) |
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(6) |
Dec
(4) |
| 2011 |
Jan
(4) |
Feb
(18) |
Mar
(9) |
Apr
(7) |
May
(6) |
Jun
(13) |
Jul
(11) |
Aug
(7) |
Sep
(12) |
Oct
(28) |
Nov
(12) |
Dec
(11) |
| 2012 |
Jan
(20) |
Feb
(21) |
Mar
(19) |
Apr
(12) |
May
(44) |
Jun
(23) |
Jul
(14) |
Aug
(26) |
Sep
(23) |
Oct
(7) |
Nov
(42) |
Dec
(15) |
| 2013 |
Jan
(62) |
Feb
(20) |
Mar
(14) |
Apr
(52) |
May
(29) |
Jun
(46) |
Jul
(20) |
Aug
(55) |
Sep
(27) |
Oct
(53) |
Nov
(29) |
Dec
(21) |
| 2014 |
Jan
(35) |
Feb
(44) |
Mar
(12) |
Apr
(37) |
May
(24) |
Jun
(17) |
Jul
(13) |
Aug
(1) |
Sep
(4) |
Oct
(13) |
Nov
(1) |
Dec
(1) |
| 2015 |
Jan
(11) |
Feb
(8) |
Mar
(10) |
Apr
(7) |
May
(17) |
Jun
(11) |
Jul
(13) |
Aug
(14) |
Sep
(6) |
Oct
(3) |
Nov
(7) |
Dec
(3) |
| 2016 |
Jan
(1) |
Feb
(4) |
Mar
(8) |
Apr
(2) |
May
(2) |
Jun
(10) |
Jul
|
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
|
From: Marcel O. <mar...@gm...> - 2014-04-01 18:35:19
|
I have a (Groovy) resteasy resource like:
@POST
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
def create(CustomerRequestBody body) {
def customer = new Customer()
bindData(customer, body)
def violations = validate(customer)
if (violations) {
return
Response.status(BAD_REQUEST).entity(toJSONArray(violations)).build()
} else {
customer.save()
return
Response.status(OK).entity(toJSONObject(customer)).build()
}
}
The resource only accepts json requests.
The CustomerRequestBody is a simple POJO (or POGO in my case).
When I post a empty response to the this resource (even with content type
set to json) I would expect a 415 unsupported media type.
However the actual is that the request ends up in the resource but the
CustomerRequestBody body variable is null.
What is the best way to globally disallow the payload to be empty and
return a 415?
Note that sending {} to the resource works as expected and the
CustomerRequestBody body variable is not empty; only it's properties are
empty as expected.
Cheers,
Marcel
|
|
From: Bill B. <bb...@re...> - 2014-04-01 13:11:18
|
Youll have to upgrade Apache Client to 4.2.1 or higher too. On 3/31/2014 10:48 PM, Ming Hsieh wrote: > Hi All > > Just downloaded 3.0.7, followed the instructions in > examples/oauth2-as7-example, updated modules, properties, configurations > and standalone.xml tried to deploy. > > auth-server.war and database.war deployed ok. > deployment failed at "customer-portal.war": > 09:58:15,925 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-4) JBA > S015876: Starting deployment of "customer-portal.war" > 09:58:16,008 ERROR [org.apache.catalina.core.StandardContext] (MSC > service threa > d 1-2) Context [/customer-portal] startup failed due to previous errors: > java.la <http://java.la> > ng.NoClassDefFoundError: > org/apache/http/impl/conn/PoolingClientConnectionManage > r > at > org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.initDefaultEngi > ne(ResteasyClientBuilder.java:428) [resteasy-client-3.0.7.Final.jar:] > at > org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyC > lientBuilder.java:333) [resteasy-client-3.0.7.Final.jar:] > at > org.jboss.resteasy.skeleton.key.as7.OAuthManagedResourceValve.init(OA > uthManagedResourceValve.java:115) [skeleton-key-as7-3.0.7.Final.jar:] > at > org.jboss.resteasy.skeleton.key.as7.OAuthManagedResourceValve.lifecyc > leEvent(OAuthManagedResourceValve.java:66) > [skeleton-key-as7-3.0.7.Final.jar:] > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl > eSupport.java:115) [jbossweb-7.0.13.Final.jar:] > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:3 > 845) [jbossweb-7.0.13.Final.jar:] > at > org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentS > ervice.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se > rviceControllerImpl.java:1811) > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont > rollerImpl.java:1746) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor. > java:1145) [rt.jar:1.7.0_25] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > .java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > > I am Using jboss 7.1.1.Final, resteasy 3.0.7.Final and jdk 1.7.0_25. > > Digged into the documentation for httpcomponents > https://hc.apache.org/httpcomponents-client-4.3.x/httpclient/apidocs/org/apache/http/impl/conn/PoolingClientConnectionManager.html > it seems like PoolingClientConnectionManager is only available in > version 4.2. > jboss as 7.1.1.Final only includes httpcomponents version 4.1.2. > Updated the httpcomponents in jboss (module.xml): > <module xmlns="urn:jboss:module:1.1" name="org.apache.httpcomponents"> > <properties> > <property name="jboss.api" value="private"/> > </properties> > > <resources> > <resource-root path="httpclient-4.3.3.jar"/> > <resource-root path="httpcore-4.3.2.jar"/> > <resource-root path="httpmime-4.3.3.jar"/> > <!-- Insert resources here --> > </resources> > > <dependencies> > <module name="javax.api"/> > <module name="org.apache.commons.codec"/> > <module name="org.apache.commons.logging"/> > <module name="org.apache.james.mime4j"/> > </dependencies> > </module> > > After that deployment success. So maybe the updated modules should be > included resteasy download. > > For anybody that is interested in oauth2. > > Regards, > > Ming > > > > On Mon, Mar 31, 2014 at 11:30 PM, Bill Burke <bb...@re... > <mailto:bb...@re...>> wrote: > > Ron fixed a few bugs in validation. Netty improvements. A few other > bug fixes here and there. > > As usual, follow links from jboss.org/resteasy > <http://jboss.org/resteasy> to download and view > documentation and release notes. > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > > ------------------------------------------------------------------------------ > _______________________________________________ > Resteasy-users mailing list > Res...@li... > <mailto:Res...@li...> > https://lists.sourceforge.net/lists/listinfo/resteasy-users > > > > > -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |
|
From: andrew s. <and...@gm...> - 2014-04-01 05:58:52
|
I've hit a well-known problem with cross site scripting; I'd like to develop javascript locally, but using REST services hosted remotely http://stackoverflow.com/questions/14589031/ajax-request-with-jax-rs-resteasy-implementing-cors I've tried a number of ways of implementing an OPTIONS method that allows clients from other origins to collect, but none of them seem to work. I've tried curl to confirm with curl, but don't see the access-control-* headers returned; my suspicion is that the @path directives are somehow not matching my request. Does anyone have a pointer to an example which works with a recent version of RestEasy (I'm using 3.0.6 and JBoss AS 7.1.1) Thanks.. Andrew |
|
From: Ming H. <min...@fu...> - 2014-04-01 02:48:41
|
Hi All
Just downloaded 3.0.7, followed the instructions in
examples/oauth2-as7-example, updated modules, properties, configurations
and standalone.xml tried to deploy.
auth-server.war and database.war deployed ok.
deployment failed at "customer-portal.war":
09:58:15,925 INFO [org.jboss.as.server.deployment] (MSC service thread
1-4) JBA
S015876: Starting deployment of "customer-portal.war"
09:58:16,008 ERROR [org.apache.catalina.core.StandardContext] (MSC service
threa
d 1-2) Context [/customer-portal] startup failed due to previous errors:
java.la
ng.NoClassDefFoundError:
org/apache/http/impl/conn/PoolingClientConnectionManage
r
at
org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.initDefaultEngi
ne(ResteasyClientBuilder.java:428) [resteasy-client-3.0.7.Final.jar:]
at
org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyC
lientBuilder.java:333) [resteasy-client-3.0.7.Final.jar:]
at
org.jboss.resteasy.skeleton.key.as7.OAuthManagedResourceValve.init(OA
uthManagedResourceValve.java:115) [skeleton-key-as7-3.0.7.Final.jar:]
at
org.jboss.resteasy.skeleton.key.as7.OAuthManagedResourceValve.lifecyc
leEvent(OAuthManagedResourceValve.java:66)
[skeleton-key-as7-3.0.7.Final.jar:]
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:115) [jbossweb-7.0.13.Final.jar:]
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3
845) [jbossweb-7.0.13.Final.jar:]
at
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentS
ervice.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1746)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1145) [rt.jar:1.7.0_25]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
I am Using jboss 7.1.1.Final, resteasy 3.0.7.Final and jdk 1.7.0_25.
Digged into the documentation for httpcomponents
https://hc.apache.org/httpcomponents-client-4.3.x/httpclient/apidocs/org/apache/http/impl/conn/PoolingClientConnectionManager.html
it seems like PoolingClientConnectionManager is only available in version
4.2.
jboss as 7.1.1.Final only includes httpcomponents version 4.1.2.
Updated the httpcomponents in jboss (module.xml):
<module xmlns="urn:jboss:module:1.1" name="org.apache.httpcomponents">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="httpclient-4.3.3.jar"/>
<resource-root path="httpcore-4.3.2.jar"/>
<resource-root path="httpmime-4.3.3.jar"/>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api"/>
<module name="org.apache.commons.codec"/>
<module name="org.apache.commons.logging"/>
<module name="org.apache.james.mime4j"/>
</dependencies>
</module>
After that deployment success. So maybe the updated modules should be
included resteasy download.
For anybody that is interested in oauth2.
Regards,
Ming
On Mon, Mar 31, 2014 at 11:30 PM, Bill Burke <bb...@re...> wrote:
> Ron fixed a few bugs in validation. Netty improvements. A few other
> bug fixes here and there.
>
> As usual, follow links from jboss.org/resteasy to download and view
> documentation and release notes.
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
|
|
From: Bill B. <bb...@re...> - 2014-03-31 16:21:02
|
Ron fixed a few bugs in validation. Netty improvements. A few other bug fixes here and there. As usual, follow links from jboss.org/resteasy to download and view documentation and release notes. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |
|
From: Ming H. <min...@fu...> - 2014-03-27 04:15:26
|
Hello everyone
Searched on the mailing list and nobody seems to have the same error as me.
Downloaded jboss as 7.1.1 and resteasy 3.0.4.Final
Followed the README in the resteasy examples/oauth2-as7-example:
1. updated the modules in jbossas/modules with the ones from resteasy.
2. copied *.ts, *.jks, *.properties from
examples/oauth2-as7-example/standalone/configuration to
jbossas/standalone/configuration
3. modified jbossas/standalone.xml
4. tried to deploy the apps cd examples/oauth2-as7-example ; mvn clean
install jboss-as:deploy
Got the following WARN in jbossas:
10:38:16,350 WARN [org.jboss.modules] (MSC service thread 1-8) Failed to
define
class org.jboss.resteasy.plugins.validation.ValidatorContextResolver in
Module
"org.jboss.resteasy.resteasy-validator-provider-11:main" from local module
loade
r @690cbe41 (roots: D:\software\jboss-as-7.1.1.Final\modules):
org.jboss.modules
.ModuleLoadError: Module com.fasterxml.classmate:main is not found in local
modu
le loader @690cbe41 (roots: D:\software\jboss-as-7.1.1.Final\modules)
at
org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.jav
a:78)
at org.jboss.modules.Module.getPathsUnchecked(Module.java:1166)
at org.jboss.modules.Module.loadModuleClass(Module.java:512)
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:
182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Con
currentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(Concu
rrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentCl
assLoader.java:398)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoad
er.java:120)
at java.lang.ClassLoader.defineClass1(Native Method)
[rt.jar:1.7.0_25]
at java.lang.ClassLoader.defineClass(ClassLoader.java:792)
[rt.jar:1.7.0
_25]
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14
2) [rt.jar:1.7.0_25]
at
org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLo
ader.java:327)
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.jav
a:391)
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.
java:243)
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoade
r.java:73)
at org.jboss.modules.Module.loadModuleClass(Module.java:517)
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:
182)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(Con
currentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(Concu
rrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentCl
assLoader.java:398)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoad
er.java:120)
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProvider
s(RegisterBuiltin.java:69) [resteasy-jaxrs-3.0.4.Final.jar:]
at
org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(Registe
rBuiltin.java:31) [resteasy-jaxrs-3.0.4.Final.jar:]
at
org.jboss.resteasy.spi.ResteasyProviderFactory.getInstance(ResteasyPr
oviderFactory.java:609) [resteasy-jaxrs-3.0.4.Final.jar:]
at
org.jboss.resteasy.skeleton.key.as7.OAuthAuthenticationServerValve.in
it(OAuthAuthenticationServerValve.java:311)
[skeleton-key-as7-3.0.4.Final.jar:]
at
org.jboss.resteasy.skeleton.key.as7.OAuthAuthenticationServerValve.li
fecycleEvent(OAuthAuthenticationServerValve.java:200) [
skeleton-key-as7-3.0.4.Fi
nal.jar:]
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:115) [jbossweb-7.0.13.Final.jar:]
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3
845) [jbossweb-7.0.13.Final.jar:]
at
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentS
ervice.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
rviceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
rollerImpl.java:1746)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1145) [rt.jar:1.7.0_25]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
10:38:16,370 WARN [org.jboss.resteasy.plugins.providers.RegisterBuiltin]
(MSC s
ervice thread 1-8) ClassNotFoundException: Unable to load builtin provider:
org.
jboss.resteasy.plugins.validation.ValidatorContextResolver
Server hangs not responding had to kill it and the upon restart the app is
still not deployed.
Tried it many times with clean install but same result.
Thanks in advance,
Ming
|
|
From: Bill B. <bb...@re...> - 2014-03-26 13:42:49
|
We don't do it right now. Maybe something like this?
ResteasyClient client = ...;
FailoverTarget target = client.failoverTarget()
.addBase("http://localhost:8080")
.addBase("http://localhost:8081")
.addBase("http://localhost:8082");
Then from Failovertarget you could do anything that a WebTarget could do.
Sound like a good API? Feel like working on it? :)
On 3/26/2014 5:21 AM, Borut Bolčina wrote:
> Hello,
>
> is failover client support somewhere in the pipeline?
>
> Like http://cxf.apache.org/docs/jax-rs-failover.html
>
> How do you guys do it now?
>
> Regards,
> borut
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
>
>
>
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
|
|
From: Borut B. <bor...@gm...> - 2014-03-26 09:21:35
|
Hello, is failover client support somewhere in the pipeline? Like http://cxf.apache.org/docs/jax-rs-failover.html How do you guys do it now? Regards, borut |
|
From: John D. A. <joh...@gm...> - 2014-03-16 23:37:32
|
Just to close the loop on this - yes, cookies are stored by default. Made my life much easier. One other question. I'm essentially building a standalone client to my main app, one that's pretty independent and meant to run standalone (either in an SE runtime or a pure servlet container). I'm trying to keep the client as small as possible. One thing I noticed is that resteasy-jaxrs is brought in by resteasy-jaxrs-client. I'm assuming this is by design due to some of the shared capabilities of client and server. Is this whole JAR really necessary though? Is there perhaps a smaller set of packages I could use, and shade into a custom JAR I'm building? John On Sun, Mar 9, 2014 at 8:26 PM, Bill Burke <bb...@re...> wrote: > I don't remember if cookie caching is on by default. Resteasy client is > based on Apache Http Client and you can definitely turn on cookie > caching there. I should probably add some high level Resteasy switch > for this too. > > > On 3/9/2014 8:22 PM, John D. Ament wrote: >> Hi all, >> >> Assuming that I'm using the RESTeasy JAX-RS 2.0 client APIs with proxy >> support, is there a way to maintain cookies between requests? Or is >> there a way to read cookies from the response and pass in as request >> params? >> >> John >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book today! >> http://p.sf.net/sfu/13534_NeoTech >> _______________________________________________ >> Resteasy-users mailing list >> Res...@li... >> https://lists.sourceforge.net/lists/listinfo/resteasy-users >> > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users |
|
From: Bill B. <bb...@re...> - 2014-03-10 13:25:20
|
And what is your client proxy class? You can only pass in an interface you know, right? On 3/10/2014 7:07 AM, Wessel Pieterse wrote: > Hi > > Thank you for the response! > > I added a code snippet of the class here : > https://gist.github.com/jimfromsa/fc88297bf5aca811eba8 . I just removed > some of the more sensitive stuff. > > Kind Regards > > > On Fri, Mar 7, 2014 at 12:32 AM, Anthony Whitford <an...@wh... > <mailto:an...@wh...>> wrote: > > I suspect there is an issue with the TokenEndpoint class. Can you > provide the interface definition? > > > > On Mar 5, 2014, at 5:24 AM, Wessel Pieterse > <we...@or... <mailto:we...@or...>> wrote: > > > > HI > > > > > > > > Was wondering if soemone has any advice for the following? > > > > Im using Resteasy 3.0.6.Final. Jboss Wildfly. > > > > ResteasyWebTarget target = client.target(contextPath + > RESOURCE_PREFIX); > > tokenEndpoint = target.proxy(TokenEndpoint.class); > > > > fails when trying to proxy the class: > > > > Here is my error : > > > > java.lang.RuntimeException: You must use at least one, but no > more than one http method annotation on: public final void > java.lang.Object.wait(long,int) throws java.lang.InterruptedException > > at > org.jboss.resteasy.client.jaxrs.ProxyBuilder.createClientInvoker(ProxyBuilder.java:76) > > at > org.jboss.resteasy.client.jaxrs.ProxyBuilder.proxy(ProxyBuilder.java:52) > > at > org.jboss.resteasy.client.jaxrs.ProxyBuilder.build(ProxyBuilder.java:120) > > at > org.jboss.resteasy.client.jaxrs.internal.ClientWebTarget.proxy(ClientWebTarget.java:72) > > at > com.unijunction.ordercloud.security.oauth.rest.TokenEndpointTest.setUp(TokenEndpointTest.java:107) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > > at > org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > > at > org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > > at > org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > > at > org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > > at > org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > > at > org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > > at > org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > > at > org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > > at > org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > > at > org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > > at > org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > > at > org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > > at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > > at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > > at > org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > > at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > > at > org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > > at > org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > > at > org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > > at > org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > > at > org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > > > > > > Any help will be greatly appreciated. Thank your for your time. > > > > Kind Regards > > > > Wessel Pieterse > > > > -- > > > > > ------------------------------------------------------------------------------ > > Subversion Kills Productivity. Get off Subversion & Make the Move > to Perforce. > > With Perforce, you get hassle-free workflows. Merge that actually > works. > > Faster operations. Version large binaries. Built-in WAN > optimization and the > > freedom to use Git, Perforce or both. Make the move to Perforce. > > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > > _______________________________________________ > > Resteasy-users mailing list > > Res...@li... > <mailto:Res...@li...> > > https://lists.sourceforge.net/lists/listinfo/resteasy-users > > > > > -- > > Ordercloud <http://www.ordercloud.co.za>Integrated Order Fulfillment SaaS > > Wessel Pieterse | Co-Founder & Software Engineer > +27 82 786 8336 | we...@or... > <mailto:we...@or...> | Twitter > <http://twitter.com/pieterse_wessel> Linkedin > <http://za.linkedin.com/in/wesselpieterse/> Skype <http://jimfromsa> > > Office: +27 21 808 9495 | www.ordercloud.co.za > <http://www.ordercloud.co.za> > Launch Lab, Admin A, Ryneveldt Street, Stellenbosch > > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > > > > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users > -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |
|
From: Wessel P. <we...@or...> - 2014-03-10 11:34:57
|
Hi Thank you for the response! I added a code snippet of the class here : https://gist.github.com/jimfromsa/fc88297bf5aca811eba8 . I just removed some of the more sensitive stuff. Kind Regards On Fri, Mar 7, 2014 at 12:32 AM, Anthony Whitford <an...@wh...>wrote: > I suspect there is an issue with the TokenEndpoint class. Can you provide > the interface definition? > > > > On Mar 5, 2014, at 5:24 AM, Wessel Pieterse <we...@or...> > wrote: > > > > HI > > > > > > > > Was wondering if soemone has any advice for the following? > > > > Im using Resteasy 3.0.6.Final. Jboss Wildfly. > > > > ResteasyWebTarget target = client.target(contextPath + RESOURCE_PREFIX); > > tokenEndpoint = target.proxy(TokenEndpoint.class); > > > > fails when trying to proxy the class: > > > > Here is my error : > > > > java.lang.RuntimeException: You must use at least one, but no more than > one http method annotation on: public final void > java.lang.Object.wait(long,int) throws java.lang.InterruptedException > > at > org.jboss.resteasy.client.jaxrs.ProxyBuilder.createClientInvoker(ProxyBuilder.java:76) > > at > org.jboss.resteasy.client.jaxrs.ProxyBuilder.proxy(ProxyBuilder.java:52) > > at > org.jboss.resteasy.client.jaxrs.ProxyBuilder.build(ProxyBuilder.java:120) > > at > org.jboss.resteasy.client.jaxrs.internal.ClientWebTarget.proxy(ClientWebTarget.java:72) > > at > com.unijunction.ordercloud.security.oauth.rest.TokenEndpointTest.setUp(TokenEndpointTest.java:107) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > > at > org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > > at > org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > > at > org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > > at > org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > > at > org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at > org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > > at > org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > > at > org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > > at > org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > > at > org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > > at > org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > > at > org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > > at > org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > > at > org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > > at > org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > > at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > > at > org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > > at > org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > > at > org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > > at > org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > > > > > > Any help will be greatly appreciated. Thank your for your time. > > > > Kind Regards > > > > Wessel Pieterse > > > > -- > > > > > ------------------------------------------------------------------------------ > > Subversion Kills Productivity. Get off Subversion & Make the Move to > Perforce. > > With Perforce, you get hassle-free workflows. Merge that actually works. > > Faster operations. Version large binaries. Built-in WAN optimization > and the > > freedom to use Git, Perforce or both. Make the move to Perforce. > > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > > _______________________________________________ > > Resteasy-users mailing list > > Res...@li... > > https://lists.sourceforge.net/lists/listinfo/resteasy-users > -- [image: Ordercloud] <http://www.ordercloud.co.za>Integrated Order Fulfillment SaaS Wessel Pieterse | Co-Founder & Software Engineer +27 82 786 8336 | we...@or... | [image: Twitter]<http://twitter.com/pieterse_wessel> [image: Linkedin] <http://za.linkedin.com/in/wesselpieterse/> [image: Skype] <http://jimfromsa> Office: +27 21 808 9495 | www.ordercloud.co.za Launch Lab, Admin A, Ryneveldt Street, Stellenbosch |
|
From: Bill B. <bb...@re...> - 2014-03-10 00:26:49
|
I don't remember if cookie caching is on by default. Resteasy client is based on Apache Http Client and you can definitely turn on cookie caching there. I should probably add some high level Resteasy switch for this too. On 3/9/2014 8:22 PM, John D. Ament wrote: > Hi all, > > Assuming that I'm using the RESTeasy JAX-RS 2.0 client APIs with proxy > support, is there a way to maintain cookies between requests? Or is > there a way to read cookies from the response and pass in as request > params? > > John > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users > -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |
|
From: John D. A. <joh...@gm...> - 2014-03-10 00:22:39
|
Hi all, Assuming that I'm using the RESTeasy JAX-RS 2.0 client APIs with proxy support, is there a way to maintain cookies between requests? Or is there a way to read cookies from the response and pass in as request params? John |
|
From: Anthony W. <an...@wh...> - 2014-03-06 22:33:26
|
I suspect there is an issue with the TokenEndpoint class. Can you provide the interface definition? > On Mar 5, 2014, at 5:24 AM, Wessel Pieterse <we...@or...> wrote: > > HI > > > > Was wondering if soemone has any advice for the following? > > Im using Resteasy 3.0.6.Final. Jboss Wildfly. > > ResteasyWebTarget target = client.target(contextPath + RESOURCE_PREFIX); > tokenEndpoint = target.proxy(TokenEndpoint.class); > > fails when trying to proxy the class: > > Here is my error : > > java.lang.RuntimeException: You must use at least one, but no more than one http method annotation on: public final void java.lang.Object.wait(long,int) throws java.lang.InterruptedException > at org.jboss.resteasy.client.jaxrs.ProxyBuilder.createClientInvoker(ProxyBuilder.java:76) > at org.jboss.resteasy.client.jaxrs.ProxyBuilder.proxy(ProxyBuilder.java:52) > at org.jboss.resteasy.client.jaxrs.ProxyBuilder.build(ProxyBuilder.java:120) > at org.jboss.resteasy.client.jaxrs.internal.ClientWebTarget.proxy(ClientWebTarget.java:72) > at com.unijunction.ordercloud.security.oauth.rest.TokenEndpointTest.setUp(TokenEndpointTest.java:107) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > > > Any help will be greatly appreciated. Thank your for your time. > > Kind Regards > > Wessel Pieterse > > -- > > ------------------------------------------------------------------------------ > Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and the > freedom to use Git, Perforce or both. Make the move to Perforce. > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users |
|
From: Alexandros A. <ant...@gm...> - 2014-03-06 14:43:52
|
I use RestEasy to develop a web application. I have a class that extends javax.ws.rs.core.Application and registers the REST services. After the creation and (full) initialization of all the services I want to execute some methods of these services. These methods may call other methods of the service using the REST API. The problem is that until the moment that my subclass of javax.ws.rs.core.Application is initialized (end of constructor) the REST API is not available (calls using REST API block) so it is not possible to call the methods after the service initialization. I also, tried using org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap without success. Also, ServletContextListener.contextInitialized seems to be executed earlier than the javax.ws.rs.core.Application.init so there are no references to the service objects. In general, I am looking for a clean way to execute code right after the services are available/deployed. Is there any way to be notified for such an event? Thank you, Alex |
|
From: Wessel P. <we...@or...> - 2014-03-05 14:20:16
|
HI
Was wondering if soemone has any advice for the following?
Im using Resteasy 3.0.6.Final. Jboss Wildfly.
ResteasyWebTarget target = client.target(contextPath + RESOURCE_PREFIX);
tokenEndpoint = target.proxy(TokenEndpoint.class);
fails when trying to proxy the class:
Here is my error :
java.lang.RuntimeException: You must use at least one, but no more than one
http method annotation on: public final void
java.lang.Object.wait(long,int) throws java.lang.InterruptedException
at
org.jboss.resteasy.client.jaxrs.ProxyBuilder.createClientInvoker(ProxyBuilder.java:76)
at org.jboss.resteasy.client.jaxrs.ProxyBuilder.proxy(ProxyBuilder.java:52)
at org.jboss.resteasy.client.jaxrs.ProxyBuilder.build(ProxyBuilder.java:120)
at
org.jboss.resteasy.client.jaxrs.internal.ClientWebTarget.proxy(ClientWebTarget.java:72)
at
com.unijunction.ordercloud.security.oauth.rest.TokenEndpointTest.setUp(TokenEndpointTest.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
at
org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
at
org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at
org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
at
org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at
org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at
org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at
org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:222)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240)
at
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
Any help will be greatly appreciated. Thank your for your time.
Kind Regards
Wessel Pieterse
--
|
|
From: Bill B. <bb...@re...> - 2014-02-28 15:37:25
|
"Mr. Burke" lol...my kid's friends don't even call me that. :) Thanks
for the writeup.
On 2/28/2014 9:14 AM, J Coder wrote:
> Mr. Burke and I had a conversation that stemmed from this question but
> it never made it's way onto the mailing list. I've summarized the
> discussion and I'm posting it here so others can benefit from his wisdom.
>
> J
>
> -------------------------------------------------------------------------------
>
> From: Coder
>
> I do have a follow up question if you have a few more moments. If not, I
> understand. I don't want to monopolize too much of your time.
>
>> I'm saying that GET /cars/honda would return a reprsentation that had
>> links to the actions. Then the client knows which URL to invoke from
>> the representation of the car instead of having to know the URL scheme.
>
> This makes sense, but I have a question about this approach. Since this
> saves the client from needing to know the URL scheme beyond the basic
> resource retrieval, I have to assume that the same concept extends to
> required parameters and possible values, otherwise, saving the client
> from needing to know the scheme isn't 'full serve'.
>
> So, given this URL that would have come back as a copy action from the
> original GET /file/{file_id}:
>
>> POST /file/{file_id}/copy
>> Content-Type: application/json
>>
>> {
>> "from" : "dir1",
>> "to" : "dir2"
>> }
>
> Where would the information for the from and to parameters, plus the
> potential dir values come from? Would those be something that would have
> come back from a different call that is perhaps associated to the form
> (or client interface), rather than to the individual resource that was
> retrieved? Perhaps it depends on the application context?
>
> Thanks!
>
> J
>
> -------------------------------------------------------------------------------
>
> From: Burke
>
>> I see. So, in your example, a representation of an assembled honda might be returned by a call to POST /cars/honda/assemble?
>
> I'm saying that GET /cars/honda would return a reprsentation that had
> links to the actions. Then the client knows which URL to invoke from the
> representation of the car instead of having to know the URL scheme.
>
>> In my case, I want to perform a file copy based on a file ID (internal representation), so I might do a call like POST /file/{file_id}/copy?from=dir1&to=dir2 and the result might be:
>
> Query parameters should be attributes of a resource only, not parameters
> for an action. Parameters for an action should be encapsulated in a
> representation:
>
> POST /file/{file_id}/copy
> Content-Type: application/json
>
> {
> "from" : "dir1",
> "to" : "dir2"
> }
>
> Response:
>
> 201
> Location: /file/new-copy-id
>
> The above doesn't have to be json. Form params are fine too.
>
> URLs should always point to something that is linkable. In your example,
> /file/{file_id}/copy?from=dir1&to=dir2 is not a linkable thing because
> it contains parameters of an action.
>
>>
>> {
>> "file": {
>> "file_id": "8477KSHIU88",
>> "locations": {
>> "location": [
>> {
>> "name": "dir1",
>> "value": "/dirs/dir1/1.2.3.txt"
>> },
>> {
>> "name": "dir2",
>> "value": "/dirs/dir2/1.2.3.txt"
>> }
>> ]
>> }
>> }
>> }
>>
>> This output might be the same as a call to GET /file/{file_id}
>>
>> Am I getting the general idea?
>
> You don't have to return the result, just a URL to it if you've created
> a new resource. Not sure I understand your example enough to know if you
> have.
>
> Honestly though, IMO, just do what's simplest to both implement and for
> clients to consume. Just stay away from adding new HTTP methods or
> embedding actions within Query parameters (JAX-RS can only dispatch by
> path).
>
> -------------------------------------------------------------------------------
>
> From: Coder
>
> I see. So, in your example, a representation of an assembled honda might
> be returned by a call to POST /cars/honda/assemble? In my case, I want
> to perform a file copy based on a file ID (internal representation), so
> I might do a call like POST /file/{file_id}/copy?from=dir1&to=dir2 and
> the result might be:
> {
> "file": {
> "file_id": "8477KSHIU88",
> "locations": {
> "location": [
> {
> "name": "dir1",
> "value": "/dirs/dir1/1.2.3.txt"
> },
> {
> "name": "dir2",
> "value": "/dirs/dir2/1.2.3.txt"
> }
> ]
> }
> }
> }
>
> This output might be the same as a call to GET /file/{file_id}
>
> Am I getting the general idea?
>
> J
>
> -------------------------------------------------------------------------------
>
> From: Burke
>
> If you have a representation for the action, then it becomes a resource
> that you could possibly link to and retrieve. It becomes even more
> important to represent the action as a URL as you can then link to the
> action:
>
> {
> "car" : "honda",
> links : {
> "assemble" : "/cars/honda/assemble"
> }
> }
>
> The client then never has to know the URL scheme, only the data format.
>
> -------------------------------------------------------------------------------
>
> From: Coder
>
> Understood. It adds no value to extend a concept if some implementations
> can't make use of it.
>
> I struggle with the concept of putting the action in the URL because I
> have a hard time opening my mind to the idea of 'an action is a
> resource'. Hard for me to let go of the 'R' in URL in other words.
>
> If this is the defacto approach however, it makes sense to give client
> developers what they expect so it remains consistent and intuitive.
>
> Much thanks for your time, Bill. The advice is appreciated.
>
> J
>
> -------------------------------------------------------------------------------
>
> From: Burke
>
> I don't suggest that approach. Instead, put the action in the URL.
>
> i.e.
>
> POST /cars/honda/assemble
> Content-Type: application/work-order+json
>
> Some clients or servers and/or their APIs might have issues dealing with
> non-standard HTTP methods. Plus HTTP methods have well defined semantics
> that client developers will expect to be followed. i.e. PUT/GET/DELETE
> is supposed to be idempotent.
>
> -------------------------------------------------------------------------------
>
> From: Coder
>
> Wonderful! Thank you very much, this is exactly what I was hoping for. I
> was incorrectly assuming that the method had to be annotated with one of
> the pre-defined values. I am not sold, in general, on the idea of either
> treating resources as actions or as passing actions in as parameters, so
> this gives a very nice option. I suppose it should have occurred to me
> that I could just create a new annotation...
>
> Thanks,
>
> J
>
> -------------------------------------------------------------------------------
>
> From: Burke
>
> By extension-method you mean something like PATCH? Yes, JAX-RS supports
> that
>
> @HttpMethod("PATCH")
> public @interface PATCH{}
>
> -------------------------------------------------------------------------------
>
> From: Coder
>
> Can this be done?
>
> Similar to how WebDAV has PROPFIND, MOVE and COPY in addition to the
> standard GET, POST, DELETE and such.
>
> If so, a pointer to an example would be much appreciated.
>
>
>
>
> ----- Original Message -----
> From: J Coder <jc...@su...>
> To: res...@li...
> Sent: Tuesday, January 28, 2014 09:48 AM
> Subject: [Resteasy-users] Can JAX-RS support an extension-method?
>
> Can this be done?
>
> Similar to how WebDAV has PROPFIND, MOVE and COPY in addition to the
> standard GET, POST, DELETE and such.
>
> If so, a pointer to an example would be much appreciated.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
|
|
From: J C. <jc...@su...> - 2014-02-28 15:18:37
|
Mr. Burke and I had a conversation that stemmed from this question but it never made it's way onto the mailing list. I've summarized the discussion and I'm posting it here so others can benefit from his wisdom.
J
-------------------------------------------------------------------------------
From: Coder
I do have a follow up question if you have a few more moments. If not, I understand. I don't want to monopolize too much of your time.
> I'm saying that GET /cars/honda would return a reprsentation that had
> links to the actions. Then the client knows which URL to invoke from
> the representation of the car instead of having to know the URL scheme.
This makes sense, but I have a question about this approach. Since this saves the client from needing to know the URL scheme beyond the basic resource retrieval, I have to assume that the same concept extends to required parameters and possible values, otherwise, saving the client from needing to know the scheme isn't 'full serve'.
So, given this URL that would have come back as a copy action from the original GET /file/{file_id}:
> POST /file/{file_id}/copy
> Content-Type: application/json
>
> {
> "from" : "dir1",
> "to" : "dir2"
> }
Where would the information for the from and to parameters, plus the potential dir values come from? Would those be something that would have come back from a different call that is perhaps associated to the form (or client interface), rather than to the individual resource that was retrieved? Perhaps it depends on the application context?
Thanks!
J
-------------------------------------------------------------------------------
From: Burke
> I see. So, in your example, a representation of an assembled honda might be returned by a call to POST /cars/honda/assemble?
I'm saying that GET /cars/honda would return a reprsentation that had links to the actions. Then the client knows which URL to invoke from the representation of the car instead of having to know the URL scheme.
> In my case, I want to perform a file copy based on a file ID (internal representation), so I might do a call like POST /file/{file_id}/copy?from=dir1&to=dir2 and the result might be:
Query parameters should be attributes of a resource only, not parameters for an action. Parameters for an action should be encapsulated in a representation:
POST /file/{file_id}/copy
Content-Type: application/json
{
"from" : "dir1",
"to" : "dir2"
}
Response:
201
Location: /file/new-copy-id
The above doesn't have to be json. Form params are fine too.
URLs should always point to something that is linkable. In your example, /file/{file_id}/copy?from=dir1&to=dir2 is not a linkable thing because it contains parameters of an action.
>
> {
> "file": {
> "file_id": "8477KSHIU88",
> "locations": {
> "location": [
> {
> "name": "dir1",
> "value": "/dirs/dir1/1.2.3.txt"
> },
> {
> "name": "dir2",
> "value": "/dirs/dir2/1.2.3.txt"
> }
> ]
> }
> }
> }
>
> This output might be the same as a call to GET /file/{file_id}
>
> Am I getting the general idea?
You don't have to return the result, just a URL to it if you've created a new resource. Not sure I understand your example enough to know if you have.
Honestly though, IMO, just do what's simplest to both implement and for clients to consume. Just stay away from adding new HTTP methods or embedding actions within Query parameters (JAX-RS can only dispatch by path).
-------------------------------------------------------------------------------
From: Coder
I see. So, in your example, a representation of an assembled honda might be returned by a call to POST /cars/honda/assemble? In my case, I want to perform a file copy based on a file ID (internal representation), so I might do a call like POST /file/{file_id}/copy?from=dir1&to=dir2 and the result might be:
{
"file": {
"file_id": "8477KSHIU88",
"locations": {
"location": [
{
"name": "dir1",
"value": "/dirs/dir1/1.2.3.txt"
},
{
"name": "dir2",
"value": "/dirs/dir2/1.2.3.txt"
}
]
}
}
}
This output might be the same as a call to GET /file/{file_id}
Am I getting the general idea?
J
-------------------------------------------------------------------------------
From: Burke
If you have a representation for the action, then it becomes a resource that you could possibly link to and retrieve. It becomes even more important to represent the action as a URL as you can then link to the action:
{
"car" : "honda",
links : {
"assemble" : "/cars/honda/assemble"
}
}
The client then never has to know the URL scheme, only the data format.
-------------------------------------------------------------------------------
From: Coder
Understood. It adds no value to extend a concept if some implementations can't make use of it.
I struggle with the concept of putting the action in the URL because I have a hard time opening my mind to the idea of 'an action is a resource'. Hard for me to let go of the 'R' in URL in other words.
If this is the defacto approach however, it makes sense to give client developers what they expect so it remains consistent and intuitive.
Much thanks for your time, Bill. The advice is appreciated.
J
-------------------------------------------------------------------------------
From: Burke
I don't suggest that approach. Instead, put the action in the URL.
i.e.
POST /cars/honda/assemble
Content-Type: application/work-order+json
Some clients or servers and/or their APIs might have issues dealing with non-standard HTTP methods. Plus HTTP methods have well defined semantics that client developers will expect to be followed. i.e. PUT/GET/DELETE is supposed to be idempotent.
-------------------------------------------------------------------------------
From: Coder
Wonderful! Thank you very much, this is exactly what I was hoping for. I was incorrectly assuming that the method had to be annotated with one of the pre-defined values. I am not sold, in general, on the idea of either treating resources as actions or as passing actions in as parameters, so this gives a very nice option. I suppose it should have occurred to me that I could just create a new annotation...
Thanks,
J
-------------------------------------------------------------------------------
From: Burke
By extension-method you mean something like PATCH? Yes, JAX-RS supports
that
@HttpMethod("PATCH")
public @interface PATCH{}
-------------------------------------------------------------------------------
From: Coder
Can this be done?
Similar to how WebDAV has PROPFIND, MOVE and COPY in addition to the standard GET, POST, DELETE and such.
If so, a pointer to an example would be much appreciated.
----- Original Message -----
From: J Coder <jc...@su...>
To: res...@li...
Sent: Tuesday, January 28, 2014 09:48 AM
Subject: [Resteasy-users] Can JAX-RS support an extension-method?
Can this be done?
Similar to how WebDAV has PROPFIND, MOVE and COPY in addition to the standard GET, POST, DELETE and such.
If so, a pointer to an example would be much appreciated.
|
|
From: John D. A. <joh...@gm...> - 2014-02-26 00:30:12
|
Hi Ari, Actually, I was prototyping something like this a little while ago (note, I'm CC'ing resteasy-users). It's similar to something I did with Netty + RestEasy. You can see the gist here: https://gist.github.com/johnament/9220905 Originally, I figured why not use weld servlet. However, it looked like weld servlet added a lot of overhead (since it deals with everything, and I only wanted REST API support). So I ended up creating a Servlet Request Listener that created the needed context. i also started with the existing RestEasy Undertow server, however it had a few issues (used a random port, was based on API from an early beta) so I updated it based on what I saw in other examples. Let me know how it works for you. - John On Tue, Feb 25, 2014 at 6:51 PM, Ari King <ari...@gm...> wrote: > Hi John, > > No, not containers in the traditional sense. I'm interested in using > Resteasy and Weld CDI with Undertow (and the like). > > -Ari > > > On Tue, Feb 25, 2014 at 5:29 PM, John D. Ament <joh...@gm...> > wrote: >> >> Ari, >> >> Are you in a container, or ? >> >> John >> >> On Tue, Feb 25, 2014 at 3:58 PM, Ari King <ari...@gm...> >> wrote: >> > Hi, >> > >> > A few months back there was "talk" on this list of how to use Weld CDI >> > with >> > Resteasy. Does anyone know if there are any "plugins" like >> > GuiceResourceFactory or manual setup approaches to using Weld CDI with >> > Resteasy? Thanks. >> > >> > -Ari >> > >> > >> > ------------------------------------------------------------------------------ >> > Flow-based real-time traffic analytics software. Cisco certified tool. >> > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> > Customize your own dashboards, set traffic alerts and generate reports. >> > Network behavioral analysis & security monitoring. All-in-one tool. >> > >> > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk >> > _______________________________________________ >> > Resteasy-users mailing list >> > Res...@li... >> > https://lists.sourceforge.net/lists/listinfo/resteasy-users >> > > > |
|
From: John D. A. <joh...@gm...> - 2014-02-25 22:29:35
|
Ari, Are you in a container, or ? John On Tue, Feb 25, 2014 at 3:58 PM, Ari King <ari...@gm...> wrote: > Hi, > > A few months back there was "talk" on this list of how to use Weld CDI with > Resteasy. Does anyone know if there are any "plugins" like > GuiceResourceFactory or manual setup approaches to using Weld CDI with > Resteasy? Thanks. > > -Ari > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users > |
|
From: Ari K. <ari...@gm...> - 2014-02-25 20:58:55
|
Hi, A few months back there was "talk" on this list of how to use Weld CDI with Resteasy. Does anyone know if there are any "plugins" like GuiceResourceFactory or manual setup approaches to using Weld CDI with Resteasy? Thanks. -Ari |
|
From: Felipe S. <fel...@1u...> - 2014-02-23 21:23:58
|
Hi, I'd like to write a provider for the Collection+JSON format. I have written providers before, but I use Springs component-scan to load them. What are the steps to build a provider that gets just added when the dependency is found? Just as the jackson-provider does :-) Thanks, Felipe Sere |
|
From: Bill B. <bb...@re...> - 2014-02-22 12:04:37
|
You have to patch the servers in question unfortunately. On 2/22/2014 5:48 AM, andrew simpson wrote: > > I've been using resteasy within my development environment, setting the > version in my maven pom.xml file, updating the version there (currently > on 3.0.4) > > I then test on a local JBoss version, jboss-as-7.1.1.Final, and until > recently assumed I would be using the same resteasy version there, but > apparently not. > > I also use a JBoss AS server at openshift to host this publicly. I > assume the same discrepancy applies there. > > Is there any way, via my Maven pom.xml file, that I can set and force > the version to be consistent, across all three environments, or does > updating the version on the servers require manual update of the class > libraries? > > Thanks... > > > > <mailto:res...@li...> > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users > -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |
|
From: andrew s. <and...@gm...> - 2014-02-22 10:48:22
|
I've been using resteasy within my development environment, setting the version in my maven pom.xml file, updating the version there (currently on 3.0.4) I then test on a local JBoss version, jboss-as-7.1.1.Final, and until recently assumed I would be using the same resteasy version there, but apparently not. I also use a JBoss AS server at openshift to host this publicly. I assume the same discrepancy applies there. Is there any way, via my Maven pom.xml file, that I can set and force the version to be consistent, across all three environments, or does updating the version on the servers require manual update of the class libraries? Thanks... <res...@li...> |
|
From: John D. A. <joh...@gm...> - 2014-02-21 15:14:56
|
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 <Fri...@ca...> wrote: > Hi, > > -----Oorspronkelijk bericht----- >> Great stuff, but still don't understand why you guys want to roll your own app server. >> Let me take a look. You submitting a PR? > > Sounds to me like you're recreating http://dropwizard.codahale.com/ ? > > Groeten, > > Friso > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > _______________________________________________ > Resteasy-users mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-users |
10 messages has been excluded from this view by a project administrator.
