resteasy-developers — The main list for RESTEasy developers to discuss project development

Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5

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

-- 
Weinan Li


On Tuesday, May 28, 2013 at 8:56 PM, Gregor Jarisch wrote:

> Yes, that was the problem I had... still not sure why it doesn't occur anymore..
> 
Thanks for confirmation. I'll check what's going wrong. 
> 
> 
> From: "Weinan Li" <we...@re... (mailto:we...@re...)>
> To: "Gregor Jarisch" <gr...@ja... (mailto:gr...@ja...)>
> Cc: res...@li... (mailto:res...@li...)
> Sent: Tuesday, May 28, 2013 12:33:54 PM
> Subject: Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5
> 
> 
> 
> -- 
> Weinan Li
> 
> 
> 
> On Tuesday, May 28, 2013 at 4:36 PM, Gregor Jarisch wrote:
> 
> > Hi,
> > 
> > yes I have just seen it right before I created one :-)
> > 
> > I have good news and bad news as well - somehow I was able to fix it - so it works fine now for me. The bad news - I have no idea what I did to make it work..
> > It might has something to do with the maven dependencies, not sure though. I hope you are still able to reproduce it - since I think that it is a bug (due to the way it was behaving) - just cannot reproduce it anymore..
> The problem I've met is that the js-api could not be generated correctly and from server side it threw NullPointer Exception. Is that the problem you've met?
>  
> > 
> > Let me know if I can assist you anyhow..
> > 
> > Gregor
> > 
> > From: "Weinan Li" <we...@re... (mailto:we...@re...)>
> > To: "Gregor Jarisch" <gr...@ja... (mailto:gr...@ja...)>
> > Cc: res...@li... (mailto:res...@li...)
> > Sent: Tuesday, May 28, 2013 10:27:20 AM
> > Subject: Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5
> > 
> > 
> > 
> > -- 
> > Weinan Li
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > 
> > 
> > On Tuesday, May 28, 2013 at 3:27 PM, Weinan Li wrote:
> > 
> > > Hi Gregor, I've confirmed this is a bug in RESTEasy 3.x. Could you please open an issue in Jira and assign to me? Thanks! (my email on JIRA: we...@re... (mailto:we...@re...))
> > 
> > I've created one Jira to track this:
> > 
> > https://issues.jboss.org/browse/RESTEASY-877 
> > > 
> > > 
> > > -- 
> > > Weinan Li
> > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > 
> > > 
> > > On Monday, May 27, 2013 at 5:50 PM, Gregor Jarisch wrote:
> > > 
> > > > Hi there,
> > > > 
> > > > I was switching to the resteasy 3.0 beta-5 to see what's new and what impact it has on our system (migration..).
> > > > I encountered troubles when using JSAPI. The client side JS-Rest-Interfaces don't get generated anymore, like it wouldn't find my rest implementations anymore. (I didn't change any code, only replaced the libs)
> > > > According to the logs they get loaded though - but maybe to late?!
> > > > 
> > > > I use "resteasy.scan" to scan my resources - works perfectly with resteasy 2.3.*, but not with the current beta. Even handing over an implementation of javax.ws.rs.Application doesn't do it..
> > > > 
> > > > Any ideas?
> > > > 
> > > > Thanks,
> > > > Gregor
> > > > 
> > > > 
> > > > 
> > > > ------------------------------------------------------------------------------
> > > > Try New Relic Now & We'll Send You this Cool Shirt
> > > > New Relic is the only SaaS-based application performance monitoring service
> > > > that delivers powerful full stack analytics. Optimize and monitor your
> > > > browser, app, & servers with just a few lines of code. Try New Relic
> > > > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> > > > _______________________________________________
> > > > Resteasy-developers mailing list
> > > > Res...@li... (mailto:Res...@li...)
> > > > https://lists.sourceforge.net/lists/listinfo/resteasy-developers
> > > 
> > 
> > 
> 
> 

[Resteasy-developers] Setting the response http code

[Gregor J. <gr...@ja...>]

Hi there,

something that is bugging me for quite some time since using resteasy is setting the http code in the response.
In my scenario I would like to create a resource by invoking a POST request. 
After creating the resource I would like to return a 201 (created) to the client as well as a Location URI pointing to the newly created resource.

I set the 201 by injecting the HttpResponse. Unfortunately, resteasy ignores my set value an puts a 204 (No Content) instead, since the POST method's return type is void.

Back in 2.3.* I was able to achieve this by overriding the value set by resteasy in a PostProcessInterceptor. Since this is deprecated now - what other options do I have?

I am aware that I could build the Response object and return it - but this is not a clean interface definition in my opinion, since one couldn't see what's coming back only by looking at the return value of the interface.

Is there any way to set the http code without returning the Response object?

Thanks, 
Gregor

-- 
Ing. Gregor Jarisch
entrepreneurship & development

Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5

[Gregor J. <gr...@ja...>]

Yes, that was the problem I had... still not sure why it doesn't occur anymore.. 


----- Original Message -----

From: "Weinan Li" <we...@re...> 
To: "Gregor Jarisch" <gr...@ja...> 
Cc: res...@li... 
Sent: Tuesday, May 28, 2013 12:33:54 PM 
Subject: Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5 



-- 
Weinan Li 




On Tuesday, May 28, 2013 at 4:36 PM, Gregor Jarisch wrote: 


Hi, 

yes I have just seen it right before I created one :-) 

I have good news and bad news as well - somehow I was able to fix it - so it works fine now for me. The bad news - I have no idea what I did to make it work.. 
It might has something to do with the maven dependencies, not sure though. I hope you are still able to reproduce it - since I think that it is a bug (due to the way it was behaving) - just cannot reproduce it anymore.. 



The problem I've met is that the js-api could not be generated correctly and from server side it threw NullPointer Exception. Is that the problem you've met? 

<blockquote>


Let me know if I can assist you anyhow.. 

Gregor 


From: "Weinan Li" < we...@re... > 
To: "Gregor Jarisch" < gr...@ja... > 
Cc: res...@li... 
Sent: Tuesday, May 28, 2013 10:27:20 AM 
Subject: Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5 



-- 
Weinan Li 
Sent with Sparrow 



On Tuesday, May 28, 2013 at 3:27 PM, Weinan Li wrote: 
<blockquote>

Hi Gregor, I've confirmed this is a bug in RESTEasy 3.x. Could you please open an issue in Jira and assign to me? Thanks! (my email on JIRA: we...@re... ) 

</blockquote>


I've created one Jira to track this: 

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

<blockquote>



-- 
Weinan Li 
Sent with Sparrow 



On Monday, May 27, 2013 at 5:50 PM, Gregor Jarisch wrote: 
<blockquote>

Hi there, 

I was switching to the resteasy 3.0 beta-5 to see what's new and what impact it has on our system (migration..). 
I encountered troubles when using JSAPI. The client side JS-Rest-Interfaces don't get generated anymore, like it wouldn't find my rest implementations anymore. (I didn't change any code, only replaced the libs) 
According to the logs they get loaded though - but maybe to late?! 

I use "resteasy.scan" to scan my resources - works perfectly with resteasy 2.3.*, but not with the current beta. Even handing over an implementation of javax.ws.rs.Application doesn't do it.. 

Any ideas? 

Thanks, 
Gregor 



------------------------------------------------------------------------------ 
Try New Relic Now & We'll Send You this Cool Shirt 
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your 
browser, app, & servers with just a few lines of code. Try New Relic 
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may 
_______________________________________________ 
Resteasy-developers mailing list 
Res...@li... 
https://lists.sourceforge.net/lists/listinfo/resteasy-developers 

</blockquote>



</blockquote>




</blockquote>

Re: [Resteasy-developers] RestEasy and Self signed certificate

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

-- 
Weinan Li
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Tuesday, May 28, 2013 at 6:19 PM, Veeramani Kalyanasundaram wrote:

> Hi All,
>  
>   We are using RestEasy framework for invoking a https enabled Rest API. Since we are in development stage, the https server is using a self signed signature.I don't see an option in RestEasy to accept the self signed signatures. 
> 
> 
> 

I cannot see anything related with RESTEasy about SSL connection. If you are using the self-signed certificate, you can use key tool to import that cert into your client side(add it either into JVM or container), and the SSL handshake will get passed.
 
> Could you please suggest any wrapper available for this?
>   
>   Thanks
>   Veera
> 
> 
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service 
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> 
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li... (mailto:Res...@li...)
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
> 
> 

Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5

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

-- 
Weinan Li



On Tuesday, May 28, 2013 at 4:36 PM, Gregor Jarisch wrote:

> Hi,
> 
> yes I have just seen it right before I created one :-)
> 
> I have good news and bad news as well - somehow I was able to fix it - so it works fine now for me. The bad news - I have no idea what I did to make it work..
> It might has something to do with the maven dependencies, not sure though. I hope you are still able to reproduce it - since I think that it is a bug (due to the way it was behaving) - just cannot reproduce it anymore..
The problem I've met is that the js-api could not be generated correctly and from server side it threw NullPointer Exception. Is that the problem you've met?
 
> 
> 
> Let me know if I can assist you anyhow..
> 
> Gregor
> 
> From: "Weinan Li" <we...@re... (mailto:we...@re...)>
> To: "Gregor Jarisch" <gr...@ja... (mailto:gr...@ja...)>
> Cc: res...@li... (mailto:res...@li...)
> Sent: Tuesday, May 28, 2013 10:27:20 AM
> Subject: Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5
> 
> 
> 
> -- 
> Weinan Li
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> 
> 
> On Tuesday, May 28, 2013 at 3:27 PM, Weinan Li wrote:
> 
> > Hi Gregor, I've confirmed this is a bug in RESTEasy 3.x. Could you please open an issue in Jira and assign to me? Thanks! (my email on JIRA: we...@re... (mailto:we...@re...))
> 
> I've created one Jira to track this:
> 
> https://issues.jboss.org/browse/RESTEASY-877 
> > 
> > 
> > -- 
> > Weinan Li
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > 
> > 
> > On Monday, May 27, 2013 at 5:50 PM, Gregor Jarisch wrote:
> > 
> > > Hi there,
> > > 
> > > I was switching to the resteasy 3.0 beta-5 to see what's new and what impact it has on our system (migration..).
> > > I encountered troubles when using JSAPI. The client side JS-Rest-Interfaces don't get generated anymore, like it wouldn't find my rest implementations anymore. (I didn't change any code, only replaced the libs)
> > > According to the logs they get loaded though - but maybe to late?!
> > > 
> > > I use "resteasy.scan" to scan my resources - works perfectly with resteasy 2.3.*, but not with the current beta. Even handing over an implementation of javax.ws.rs.Application doesn't do it..
> > > 
> > > Any ideas?
> > > 
> > > Thanks,
> > > Gregor
> > > 
> > > 
> > > 
> > > ------------------------------------------------------------------------------
> > > Try New Relic Now & We'll Send You this Cool Shirt
> > > New Relic is the only SaaS-based application performance monitoring service
> > > that delivers powerful full stack analytics. Optimize and monitor your
> > > browser, app, & servers with just a few lines of code. Try New Relic
> > > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> > > _______________________________________________
> > > Resteasy-developers mailing list
> > > Res...@li... (mailto:Res...@li...)
> > > https://lists.sourceforge.net/lists/listinfo/resteasy-developers
> > 
> 
> 

[Resteasy-developers] RestEasy and Self signed certificate

[Veeramani K. <kve...@gm...>]

Hi All,

  We are using RestEasy framework for invoking a https enabled Rest API.
Since we are in development stage, the https server is using a self signed
signature.I don't see an option in RestEasy to accept the self signed
signatures. Could you please suggest any wrapper available for this?

  Thanks
  Veera

Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5

[Gregor J. <gr...@ja...>]

Hi, 

yes I have just seen it right before I created one :-) 

I have good news and bad news as well - somehow I was able to fix it - so it works fine now for me. The bad news - I have no idea what I did to make it work.. 
It might has something to do with the maven dependencies, not sure though. I hope you are still able to reproduce it - since I think that it is a bug (due to the way it was behaving) - just cannot reproduce it anymore.. 

Let me know if I can assist you anyhow.. 

Gregor 

----- Original Message -----

From: "Weinan Li" <we...@re...> 
To: "Gregor Jarisch" <gr...@ja...> 
Cc: res...@li... 
Sent: Tuesday, May 28, 2013 10:27:20 AM 
Subject: Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5 



-- 
Weinan Li 
Sent with Sparrow 



On Tuesday, May 28, 2013 at 3:27 PM, Weinan Li wrote: 


Hi Gregor, I've confirmed this is a bug in RESTEasy 3.x. Could you please open an issue in Jira and assign to me? Thanks! (my email on JIRA: we...@re... ) 




I've created one Jira to track this: 

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

<blockquote>



-- 
Weinan Li 
Sent with Sparrow 



On Monday, May 27, 2013 at 5:50 PM, Gregor Jarisch wrote: 
<blockquote>

Hi there, 

I was switching to the resteasy 3.0 beta-5 to see what's new and what impact it has on our system (migration..). 
I encountered troubles when using JSAPI. The client side JS-Rest-Interfaces don't get generated anymore, like it wouldn't find my rest implementations anymore. (I didn't change any code, only replaced the libs) 
According to the logs they get loaded though - but maybe to late?! 

I use "resteasy.scan" to scan my resources - works perfectly with resteasy 2.3.*, but not with the current beta. Even handing over an implementation of javax.ws.rs.Application doesn't do it.. 

Any ideas? 

Thanks, 
Gregor 



------------------------------------------------------------------------------ 
Try New Relic Now & We'll Send You this Cool Shirt 
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your 
browser, app, & servers with just a few lines of code. Try New Relic 
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may 
_______________________________________________ 
Resteasy-developers mailing list 
Res...@li... 
https://lists.sourceforge.net/lists/listinfo/resteasy-developers 

</blockquote>



</blockquote>

Re: [Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5

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

-- 
Weinan Li
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Tuesday, May 28, 2013 at 3:27 PM, Weinan Li wrote:

> Hi Gregor, I've confirmed this is a bug in RESTEasy 3.x. Could you please open an issue in Jira and assign to me? Thanks! (my email on JIRA: we...@re... (mailto:we...@re...))

I've created one Jira to track this:

https://issues.jboss.org/browse/RESTEASY-877 
> 
> 
> -- 
> Weinan Li
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> 
> 
> On Monday, May 27, 2013 at 5:50 PM, Gregor Jarisch wrote:
> 
> > Hi there,
> > 
> > I was switching to the resteasy 3.0 beta-5 to see what's new and what impact it has on our system (migration..).
> > I encountered troubles when using JSAPI. The client side JS-Rest-Interfaces don't get generated anymore, like it wouldn't find my rest implementations anymore. (I didn't change any code, only replaced the libs)
> > According to the logs they get loaded though - but maybe to late?!
> > 
> > I use "resteasy.scan" to scan my resources - works perfectly with resteasy 2.3.*, but not with the current beta. Even handing over an implementation of javax.ws.rs.Application doesn't do it..
> > 
> > Any ideas? 
> > 
> > Thanks, 
> > Gregor
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring service 
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> > _______________________________________________
> > Resteasy-developers mailing list
> > Res...@li... (mailto:Res...@li...)
> > https://lists.sourceforge.net/lists/listinfo/resteasy-developers
> > 
> > 
> > 
> 
> 

[Resteasy-developers] Init Resources - JSAPI - 3.0 beta-5

[Gregor J. <gr...@ja...>]

Hi there,

I was switching to the resteasy 3.0 beta-5 to see what's new and what impact it has on our system (migration..).
I encountered troubles when using JSAPI. The client side JS-Rest-Interfaces don't get generated anymore, like it wouldn't find my rest implementations anymore. (I didn't change any code, only replaced the libs)
According to the logs they get loaded though - but maybe to late?!

I use "resteasy.scan" to scan my resources - works perfectly with resteasy 2.3.*, but not with the current beta. Even handing over an implementation of javax.ws.rs.Application doesn't do it..

Any ideas? 

Thanks, 
Gregor

[Resteasy-developers] RESTEasy JS-API , not allowed by Access-Control-Allow-Origin???

[Alberto M. <ama...@gm...>]

Hello, I'm working on this example.

https://repository.cloudera.com/content/groups/cdh-build/org/jboss/resteasy/examples-jsapi/2.3.2.Final/examples-jsapi-2.3.2.Final.war

Client javascript to resteasy with jsapi.
=====================================================================
<html>
<body>
<h2>RESTEasy JS-API Demo</h2>
<form>
<input type='button' onclick='callJsApi();' value='Get Orders'/>
</form>

<script src="http://localhost:8080/examples-jsapi-2.3.2.Final/rest-js"
type="text/javascript"></script>
<script type="text/javascript">
var global_order_id = 0;
function callJsApi() {
var order = Orders.getOrder({id: global_order_id++});
alert(order);
}
</script>
</body>
</html>
=====================================================================

If the html or jsp client, server is out of service rest. Returns this
error in console javascript chrome:

"XMLHttpRequest can not load
http://localhost:8080/examples-jsapi-2.3.2.Final/resteasy/orders/5.
Origin null is not allowed by Access-Control-Allow-Origin.
clientAjax.html: 1
Uncaught Error: NETWORK_ERR: XMLHttpRequest Exception 101 "


works! if clientAjax.html this within the server. Please no way to
configure the rest, to accept calls from outside the server?

--
Alberto

Saludos

[Resteasy-developers] 3.0-beta-5 released

[Bill B. <bb...@re...>]

Did a bit of refactoring of the SPIs to improve generics support among 
other bug fixes.  A side effect to this is that there is now a 
programmatic interface that allows you to register un-annotated resource 
classes.  Also, bumped Jackson to 1.9.12 and also added an additional 
Jackson2 provider.  See docs for more details.

http://jboss.org/resteasy


Bill

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

Re: [Resteasy-developers] REST implementation?

[Brian M. <bri...@gm...>]

Don't forget branding.  I was looking for an easy REST framework for Java.  I picked RESTEasy because I figured they couldn't call it "RESTEasy" if it wasn't easy.  It was, we're happy, and life's great.  Thanks a bunch, BTW.

-Brian

On May 6, 2013, at 2:52 PM, Bill Burke <bb...@re...> wrote:

> I think we have some interesting security stuff too.
> 
> On 5/6/2013 3:45 PM, Solomon Duskis wrote:
>> I'd use CXF only if I had to support both SOAP and REST calls.  On the +
>> side for RESTEasy: client implementation and spring integration.
>> 
>> 
>> On Mon, May 6, 2013 at 4:13 AM, <hol...@no...
>> <mailto:hol...@no...>> wrote:
>> 
>>    Hi,____
>> 
>>    __ __
>> 
>>    I can’t say anything about CXF, but for me the biggest advantage of
>>    RESTeasy vs. Jersey is that RESTeasy can handle annotations on
>>    interfaces. Jersery won’t find those.____
>> 
>>    __ __
>> 
>>    Holger____
>> 
>>    __ __
>> 
>>    __ __
>> 
>>    *From:*Navindian [mailto:nav...@gm...
>>    <mailto:nav...@gm...>]
>>    *Sent:* Sonntag, 5. Mai 2013 18:12
>>    *To:* res...@li...
>>    <mailto:res...@li...>
>>    *Subject:* [Resteasy-developers] REST implementation?____
>> 
>>    __ __
>> 
>>    Hi____
>> 
>>    __ __
>> 
>>    I am currently developing my data services using following
>>    technologies.____
>> 
>>    __ __
>> 
>>    1. Axis2 REST____
>> 
>>    2. Spring____
>> 
>>    3. Hibernate____
>> 
>>    __ __
>> 
>>    I wish to replace AXIS 2 with the following:____
>> 
>>    1. Jersey____
>> 
>>    2. RESTeasy____
>> 
>>    3. CXF____
>> 
>>    __ __
>> 
>>    Can anyone tell me which one i have to choose and why?____
>> 
>>    __ __
>> 
>>    thanks____
>> 
>>    jyothi____
>> 
>> 
>>    ------------------------------------------------------------------------------
>>    Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>>    Get 100% visibility into your production application - at no cost.
>>    Code-level diagnostics for performance bottlenecks with <2% overhead
>>    Download for free and get started troubleshooting in minutes.
>>    http://p.sf.net/sfu/appdyn_d2d_ap1
>>    _______________________________________________
>>    Resteasy-developers mailing list
>>    Res...@li...
>>    <mailto:Res...@li...>
>>    https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and
>> their applications. This 200-page book is written by three acclaimed
>> leaders in the field. The early access version is available now.
>> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>> 
>> 
>> 
>> _______________________________________________
>> Resteasy-developers mailing list
>> Res...@li...
>> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>> 
> 
> -- 
> 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. This 200-page book is written by three acclaimed 
> leaders in the field. The early access version is available now. 
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers

Re: [Resteasy-developers] REST implementation?

[Bill B. <bb...@re...>]

I think we have some interesting security stuff too.

On 5/6/2013 3:45 PM, Solomon Duskis wrote:
> I'd use CXF only if I had to support both SOAP and REST calls.  On the +
> side for RESTEasy: client implementation and spring integration.
>
>
> On Mon, May 6, 2013 at 4:13 AM, <hol...@no...
> <mailto:hol...@no...>> wrote:
>
>     Hi,____
>
>     __ __
>
>     I can’t say anything about CXF, but for me the biggest advantage of
>     RESTeasy vs. Jersey is that RESTeasy can handle annotations on
>     interfaces. Jersery won’t find those.____
>
>     __ __
>
>     Holger____
>
>     __ __
>
>     __ __
>
>     *From:*Navindian [mailto:nav...@gm...
>     <mailto:nav...@gm...>]
>     *Sent:* Sonntag, 5. Mai 2013 18:12
>     *To:* res...@li...
>     <mailto:res...@li...>
>     *Subject:* [Resteasy-developers] REST implementation?____
>
>     __ __
>
>     Hi____
>
>     __ __
>
>     I am currently developing my data services using following
>     technologies.____
>
>     __ __
>
>     1. Axis2 REST____
>
>     2. Spring____
>
>     3. Hibernate____
>
>     __ __
>
>     I wish to replace AXIS 2 with the following:____
>
>     1. Jersey____
>
>     2. RESTeasy____
>
>     3. CXF____
>
>     __ __
>
>     Can anyone tell me which one i have to choose and why?____
>
>     __ __
>
>     thanks____
>
>     jyothi____
>
>
>     ------------------------------------------------------------------------------
>     Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>     Get 100% visibility into your production application - at no cost.
>     Code-level diagnostics for performance bottlenecks with <2% overhead
>     Download for free and get started troubleshooting in minutes.
>     http://p.sf.net/sfu/appdyn_d2d_ap1
>     _______________________________________________
>     Resteasy-developers mailing list
>     Res...@li...
>     <mailto:Res...@li...>
>     https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. This 200-page book is written by three acclaimed
> leaders in the field. The early access version is available now.
> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

Re: [Resteasy-developers] REST implementation?

[Solomon D. <sd...@gm...>]

I'd use CXF only if I had to support both SOAP and REST calls.  On the +
side for RESTEasy: client implementation and spring integration.


On Mon, May 6, 2013 at 4:13 AM, <hol...@no...> wrote:

>  Hi,****
>
> ** **
>
> I can’t say anything about CXF, but for me the biggest advantage of
> RESTeasy vs. Jersey is that RESTeasy can handle annotations on interfaces.
> Jersery won’t find those.****
>
> ** **
>
> Holger****
>
> ** **
>
> ** **
>
> *From:* Navindian [mailto:nav...@gm...]
> *Sent:* Sonntag, 5. Mai 2013 18:12
> *To:* res...@li...
> *Subject:* [Resteasy-developers] REST implementation?****
>
> ** **
>
> Hi****
>
> ** **
>
> I am currently developing my data services using following technologies.**
> **
>
> ** **
>
> 1. Axis2 REST****
>
> 2. Spring****
>
> 3. Hibernate****
>
> ** **
>
> I wish to replace AXIS 2 with the following:****
>
> 1. Jersey****
>
> 2. RESTeasy****
>
> 3. CXF****
>
> ** **
>
> Can anyone tell me which one i have to choose and why?****
>
> ** **
>
> thanks****
>
> jyothi****
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>

Re: [Resteasy-developers] REST implementation?

[<hol...@no...>]

Hi,

I can't say anything about CXF, but for me the biggest advantage of RESTeasy vs. Jersey is that RESTeasy can handle annotations on interfaces. Jersery won't find those.

Holger


From: Navindian [mailto:nav...@gm...]
Sent: Sonntag, 5. Mai 2013 18:12
To: res...@li...
Subject: [Resteasy-developers] REST implementation?

Hi

I am currently developing my data services using following technologies.

1. Axis2 REST
2. Spring
3. Hibernate

I wish to replace AXIS 2 with the following:
1. Jersey
2. RESTeasy
3. CXF

Can anyone tell me which one i have to choose and why?

thanks
jyothi

Re: [Resteasy-developers] REST implementation?

[Bill B. <bb...@re...>]

I really haven't done any research on why to pick one over the other. 
Resteasy does have a book dedicated to it.

http://oreilly.com/catalog/9780596158040/

Features?  You'll have to do your own comparison.  If you're deploying 
on JBoss though, Resteasy is your best bet.

On 5/5/2013 12:11 PM, Navindian wrote:
> Hi
>
> I am currently developing my data services using following technologies.
>
> 1. Axis2 REST
> 2. Spring
> 3. Hibernate
>
> I wish to replace AXIS 2 with the following:
> 1. Jersey
> 2. RESTeasy
> 3. CXF
>
> Can anyone tell me which one i have to choose and why?
>
> thanks
> jyothi
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

[Resteasy-developers] REST implementation?

[Navindian <nav...@gm...>]

Hi

I am currently developing my data services using following technologies.

1. Axis2 REST
2. Spring
3. Hibernate

I wish to replace AXIS 2 with the following:
1. Jersey
2. RESTeasy
3. CXF

Can anyone tell me which one i have to choose and why?

thanks
jyothi

Re: [Resteasy-developers] Encoding issue

[Bill B. <bb...@re...>]

Resteasy delegates to the servlet container to parse Form parameters.

On 4/30/2013 11:04 AM, Ove Ranheim wrote:
> Hi Bill,
>
> In working on a project where we're using a mule (3.3) client to create
> at rest request against a rest service based on resteasy 1.2.1.GA. The
> request is encoded in utf-8. From what I understand iso-8859-1 is used
> by default in a post.
> We have tried to set the content type to:
> "application/x-www-form-urlencoded ; charset=UTF-8"
> But that results in a http 500 error. If  we use:
> "application/x-www-form-urlencoded"
> The request is processed but we get garbled chars later in processing.
> Is there a way to use utf-8 encoding in the request?
>
> Cheers,
> Ove
>
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

[Resteasy-developers] load-balanced oauth2 servers

[Bill B. <bb...@re...>]

TL;DR Can't have a load-balanced set of auth servers at the moment with 
our oauth stuff.

Josh, these are good questions and something I'm going to have to think 
about.  If you've read up about OAuth2, you'll see that there's a step 
where your web-app receives an access code from the user's browser, then 
must make a separate request to the auth server to turn the access code 
into an access token.  This state cannot be stored in a session.

My initial thought is to require that each server have both its own DNS 
entry and the access code will have a callback URL within it.  The 
access code would be digitally signed so it can be verified.



On 4/30/2013 1:51 AM, Josh wrote:
> Hi Bill,
>
> I now realize my second question was a bit silly and I should not be
> trying to implement a web application using BASIC auth, but instead
> using session replication in AS7.  One problem I am running into is
> between deployments of my application it seems to be resetting the
> session store, but that is a google answer.
>
> Also I think the answer to #1 is yes.
>
> So maybe no questions after all.  Thanks for your contributions!
>
> - Josh
>
>
> On Mon, Apr 29, 2013 at 11:21 PM, Josh <sm...@gm...
> <mailto:sm...@gm...>> wrote:
>
>     Hi Bill,
>
>     Just exploring your OAuth2 implementation for RestEasy and
>     encountering some trouble wraping my head around some of these
>     ideas.  You're probably a very busy person, but I would very
>     appreciative if you could help point me in the right direction.
>
>     I plan on implementing a webpage + phone apps that all depend on a
>     central restful service implemented in cluster configuration.  I
>     plan on using a load balancing configuration where each request
>     cannot be guaranteed to get the same instance.
>
>     My questions are:
>
>     1) Can each rest service instance be an auth-server or does there
>     need to be a central auth server instance?
>
>     2) Due to load balancing session id's cannot be used to store the
>     form authentication cookies.  It is my understanding that BASIC
>     authentication could be used to store the bearer token.  I see that
>     you have examples showing how to do this in the 'client-example'
>     using the ResteasyClient.  Wondering how this would be accomplished
>     using a web browser and login form?  Is there a more obvious way to
>     be solving the cookie / load balancing issue?
>
>
>     Thanks,
>
>     Josh
>
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

[Resteasy-developers] Encoding issue

[Ove R. <ora...@gm...>]

Hi Bill,

In working on a project where we're using a mule (3.3) client to create at rest request against a rest service based on resteasy 1.2.1.GA. The request is encoded in utf-8. From what I understand iso-8859-1 is used by default in a post.
 
We have tried to set the content type to:
"application/x-www-form-urlencoded ; charset=UTF-8"
 
But that results in a http 500 error. If  we use:
"application/x-www-form-urlencoded"
 
The request is processed but we get garbled chars later in processing.
 
Is there a way to use utf-8 encoding in the request?

Cheers,
Ove

[Resteasy-developers] JAX-RS 2 Client side filters for service with interesting response codes

[Michael M. <mic...@ga...>]

Thanks Bill, that worked a treat.

On 17/04/2013 23:51, "res...@li..."
<res...@li...> wrote:

>Send Resteasy-developers mailing list submissions to
>	res...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>or, via email, send a message with subject or body 'help' to
>	res...@li...
>
>You can reach the person managing the list at
>	res...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Resteasy-developers digest..."
>
>
>Today's Topics:
>
>   1. JAX-RS 2 Client side filters for service with interesting
>      response codes (Michael McCarthy)
>   2. Re: Work on RESTEasy-795 (Weinan Li)
>   3. 2.3.6 and 3.0-beta-4 release tomorrow (Bill Burke)
>   4. 3.0-beta-4 and 2.3.6 released (Bill Burke)
>   5. Test - ignore (Ron Sigal)
>   6. spring bean processor bug (Gendler, Samuel)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 26 Mar 2013 08:21:37 +0000
>From: Michael McCarthy <mic...@ga...>
>Subject: [Resteasy-developers] JAX-RS 2 Client side filters for
>	service with interesting response codes
>To: "res...@li..."
>	<res...@li...>
>Message-ID: <CD770B0B.1A44E%mic...@ga...>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi all,
>
>I'm using the new JAX-RS 2 client API to communicate with a system that
>has an interesting take on response codes, which basically means it will
>return 200 for everything and the body will include a fault element to
>indicate something has gone wrong. As an example, given an XML response
>from a POST  to create a pet I might get:
>
><pet><name>Fido</name></pet>
>
>Or I might get
>
><fault><error-code>3423423</error-code></fault>
>
>My take on this is that I should provide an interceptor/filter to look at
>the message body response, determine if there is a fault in there, and
>throw a WebApplicationException, or at the very least change the status
>code so that a WebApplicationException is thrown further down the line..
>
>My questions are, which filter or interceptor is correct in this use
>case? I would imagine where I want it to kick in is at the point where it
>has the response body but hasn't tried to marshall it.
>
>The second question was, am I right to register it at the point I build
>my client, e.g.
>ClientBuilder.newBuilder().register(new MyCustomInterceptor()).build()
>
>The intention is that this would be a client specifically for dealing
>with the quirks of those endpoints, other clients would not have those
>filters applied. I'm leaving off the Provider annotation purposely so it
>doesn't get picked up automagically anywhere else.
>
>Appreciate any advice as ever.
>-------------- next part --------------
>An HTML attachment was scrubbed...
>
>------------------------------
>
>Message: 2
>Date: Tue, 26 Mar 2013 18:54:57 +0800
>From: Weinan Li <we...@re...>
>Subject: Re: [Resteasy-developers] Work on RESTEasy-795
>To: Michael Pasternak <mpa...@re...>
>Cc: resteasy-developers <res...@li...>
>Message-ID: <2C2...@re...>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Hi Michael,
>
>	Next release of RESTEasy 3.x will include it(3.0-beta-4).
>
>	It will not supported in 2.3.6.Final(next release of 2.3.x) because it
>breaks the @NoJackson support.
>
>	For 3.x the jettison support will be removed soon so we don't have to
>consider the backward compatibility.
>
>
>
>- Weinan Li
>JBoss, Redhat
>
>
>
>
>
>
>
>
>
>
>On Mar 26, 2013, at 4:25 PM, Michael Pasternak <mpa...@re...>
>wrote:
>
>> 
>> 
>> Hi Guys,
>> 
>> i see RESTEasy-795 is closed, in what upstream/downstream version this
>>change
>> will be available?
>> 
>> (btw thanks for fixing this)
>> 
>> On 02/27/2013 03:44 AM, Weinan Li wrote:
>>> 
>>> - Weinan Li
>>> JBoss, Redhat
>>> 
>>> 
>>> On Feb 26, 2013, at 11:37 PM, Bill Burke <bb...@re...
>>><mailto:bb...@re...>> wrote:
>>> 
>>>> We could also retire Jettison support in Resteasy 3.0.  In my book
>>>>revision I'm removing the section on Jettision and replacing it with
>>>>Jackson.
>>> 
>>> Cool! If Jettison is no longer supported, then seems my previous patch
>>>is fine to use, and I will also remove the @NoJackson support and
>>>resubmit the pull request. Does
>>> that sound reasonable ?
>>> 
>>>> 
>>>> On 2/26/2013 4:11 AM, Weinan Li wrote:
>>>>> Hi Bill,
>>>>> 
>>>>> Currently I'm working on RESTEASY-795: Add Jackson JAXB support to
>>>>>RESTEasy
>>>>> 
>>>>> Ron has helped me find out the problem of my previous patch[1] is
>>>>>that
>>>>> it will cause compatiblity problem if Jettison and Jackson co-exists
>>>>>in
>>>>> a project. We are not sure if this is the backward compatibility you
>>>>> were referring to, could you please help to confirm this?
>>>>> 
>>>>> Here is my solution to fix this: Add a @UseJackson annotation for
>>>>>user
>>>>> to annotate on JAXB annotated resources. If the JAXB resource is
>>>>> annotated by it, RESTEasy will use Jackson to deal with it,
>>>>>otherwise it
>>>>> will use Jettison. And we'll make sure @UseJackson and @NoJackson
>>>>>cannot
>>>>> be used at same time. Do you like this idea? If it's okay  I'll start
>>>>> coding.
>>>>> 
>>>>> [1]
>>>>> 
>>>>>https://github.com/resteasy/Resteasy/commit/6c1f9bd07e9b31d9b73746cad2
>>>>>f6a0b6846f42e6
>>>>> 
>>>>> - Weinan Li
>>>>> JBoss, Redhat
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> -- 
>>>> Bill Burke
>>>> JBoss, a division of Red Hat
>>>> http://bill.burkecentral.com
>>> 
>> 
>> 
>> -- 
>> 
>> Michael Pasternak
>> RedHat, ENG-Virtualization R&D
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>
>------------------------------
>
>Message: 3
>Date: Tue, 09 Apr 2013 10:38:45 -0400
>From: Bill Burke <bb...@re...>
>Subject: [Resteasy-developers] 2.3.6 and 3.0-beta-4 release tomorrow
>To: resteasy-developers <Res...@li...>
>Message-ID: <516...@re...>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>fyi
>
>-- 
>Bill Burke
>JBoss, a division of Red Hat
>http://bill.burkecentral.com
>
>
>
>------------------------------
>
>Message: 4
>Date: Wed, 10 Apr 2013 10:22:44 -0400
>From: Bill Burke <bb...@re...>
>Subject: [Resteasy-developers] 3.0-beta-4 and 2.3.6 released
>To: resteasy-developers <Res...@li...>
>Message-ID: <516...@re...>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>See jboss.org/resteasy for relevant links for downloads/documentation.
>
>3.0-beta-4 is our last beta!  JAX-RS 2.0 Final is being voted on for
>JCP.  We'll be obtaining the TCK soon and starting work on getting
>certified.  There's also some architectural work that needs to be
>finished for 3.0.  We'll have a short RC release sometime in May, then a
>3.0 Final Release early June.
>
>2.3.6 is just a maintenance release.
>
>-- 
>Bill Burke
>JBoss, a division of Red Hat
>http://bill.burkecentral.com
>
>
>
>------------------------------
>
>Message: 5
>Date: Sat, 13 Apr 2013 13:49:10 -0400
>From: Ron Sigal <rs...@re...>
>Subject: [Resteasy-developers] Test - ignore
>To: res...@li...
>Message-ID: <516...@re...>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Test.
>
>
>
>------------------------------
>
>Message: 6
>Date: Wed, 17 Apr 2013 15:35:59 -0700
>From: "Gendler, Samuel" <Sam...@we...>
>Subject: [Resteasy-developers] spring bean processor bug
>To: "'res...@li...'"
>	<res...@li...>
>Cc: "'res...@li...'"
>	<res...@li...>
>Message-ID:
>	<CD4...@PA....l
>ocal>
>	
>Content-Type: text/plain; charset="us-ascii"
>
>I recently upgraded a project from 2.2.3.GA to 2.3.6.FINAL and
>encountered a bug that appears to originate in the SpringBeanProcessor
>and which breaks property placeholder variable replacement in certain
>spring beans.
>
>I haven't completely unwound the bug to the root cause, but I've gotten
>close enough to be confident that someone with more resteasy knowledge
>can likely address it much more quickly than I can.
>
>First, the symptoms:
>
>I have a bean of class org.springframework.jndi.JndiTemplate declared as
>follows:
>
>  <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
>    <property name="environment">
>      <props>
>        <prop 
>key="java.naming.factory.initial">com.sonicsw.jndi.mfcontext.MFContextFact
>ory</prop>
>        <prop key="java.naming.provider.url">${jndi.url}</prop>
>        <prop key="java.naming.security.principal">${jndi.user}</prop>
>        <prop 
>key="java.naming.security.credentials">${jndi.password}</prop>
>        <prop 
>key="com.sonicsw.jndi.mfcontext.domain">${jndi.domain}</prop>
>        <prop key="clientId">${jndi.clientId}</prop>
>        <prop key="subscriptionDurable">true</prop>
>        <prop 
>key="durableSubscriptionName">${jndi.durableSubscriptionName}</prop>
>        <prop key="timeToLive">${jndi.timeToLive}</prop>
>        <prop 
>key="com.sonicsw.jndi.mfcontext.idleTimeout">${jndi.timeout}</prop>
>      </props>
>    </property>
>  </bean>
>
>I have a property placeholder that is most definitely initialized with
>values for all of those properties.  I can set the same values in a test
>object and see that they are correctly replaced.  However, for reasons
>that I'll get into in a moment, the jndiTemplate properties are NOT
>replaced and it receives the raw ${...} strings instead.  Needless to
>say, this breaks my project.  Switching back to 2.2.3.GA definitely fixes
>it without making any other changes.
>
>What I've discovered so far about the cause:
>
>In SpringBeanProcessor.postProcessBeanFactory(), a method called
>findResteasyRegistrations() is called.  That method, in turn, calls the
>following:
>
>beanFactory.getBeansOfType(ResteasyRegistration.class);
>
>That method call causes some beans (but not all beans) to be
>instantiated, and any beans that are instantiated at that point do not
>have property placeholder values replaced in them, because the property
>placeholder processor has (apparently) not yet executed.  What I haven't
>figured out is why my jndiTemplate bean is impacted by this, while
>another bean that I created simply to test the creation of properties
>inside of a bean definition is not.  It is apparently skipped over by the
>getBeansOfType(ResteasyRegistration.class) and property replacement
>happens correctly in that case.
>
>Initially, I suspected that this was a problem with post processor
>ordering.  This was somewhat vexing as the SpringBeanProcessor does
>implement the PriorityOrdered interface, but exposes no mechanism for
>modifying the order value.  I created my own version of
>SpringContextLoaderListener which forgoes the use of
>SpringContextLoaderSupport and performs the same work, but also calls
>setOrder(x) on the SpringBeanProcessor before adding it to the
>postprocessors and application listeners.  However, that didn't seem to
>have any impact, no matter in which relative order I placed the property
>placeholder and the spring bean processor.
>
>For one final data point, if I don't use a property placeholder, but
>instead reference a properties object via Spring-EL in the XML, then the
>values are correctly replaced, because the spring-el is evaluated when
>the xml is parsed (I assume), while property placeholders are definitely
>evaluated lazily, long after the bean definitions are created by the xml
>parsing process.
>
>  <util:properties id="jmsProperties"
>location="file:${catalina.base}/conf/jms.properties"/>
>
>  <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
>    <property name="environment">
>      <props>
>        <prop 
>key="java.naming.factory.initial">com.sonicsw.jndi.mfcontext.MFContextFact
>ory
>        </prop>
>        <prop 
>key="java.naming.provider.url">#{jmsProperties['jndi.url']}</prop>
>        <prop 
>key="java.naming.security.principal">#{jmsProperties['jndi.user']}</prop>
>        <prop 
>key="java.naming.security.credentials">#{jmsProperties['jndi.password']}</
>prop>
>        <prop 
>key="com.sonicsw.jndi.mfcontext.domain">#{jmsProperties['jndi.domain']}</p
>rop>
>        <prop key="clientId">#{jmsProperties['jndi.clientId']}</prop>
>        <prop key="subscriptionDurable">true</prop>
>        <prop 
>key="durableSubscriptionName">#{jmsProperties['jndi.durableSubscriptionNam
>e']}</prop>
>        <prop key="timeToLive">#{jmsProperties['jndi.timeToLive']}</prop>
>        <prop 
>key="com.sonicsw.jndi.mfcontext.idleTimeout">#{jmsProperties['jndi.timeout
>']}</prop>
>      </props>
>    </property>
>  </bean>
>
>This works, but is a kludge.  I'd much prefer to have
>property-placeholding actually functional, especially since it is
>apparently impossible to predict which beans will fail to have properties
>replaced.  Looking at the sourec code to jndiTemplate, I can see no
>obvious reason why it is treated differently than my own test bean.  Both
>have no annotations and both receive a java.util.Properties object as a
>property.  The behavior is consistent no matter what order they appear in
>my context xml file.
>
>I've attached my replacement SpringContextLoaderListener just for
>reference, in case someone else wants to modify the ordering of the
>placeholders while testing or fixing this.  The relevant web.xml entries
>are below:
>
>  <context-param>
>    <param-name>resteasy.postprocessor.order</param-name>
>    <param-value>0</param-value>
>  </context-param>
>
>  <listener>
>    <listener-class>
>      
>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-clas
>s>
>  </listener>
>
>  <listener>
>    <!-- 
>listener-class>org.jboss.resteasy.plugins.spring.SpringContextLoaderListen
>er</listener-class-->
>    <listener-class>
>        com.westernasset.compliance.util.SpringContextLoaderListener
>    </listener-class>
>  </listener>
>
>
>
>**********************************************************************
>E-mail sent through the Internet is not secure. Western Asset
>therefore recommends that you do not send any confidential or
>sensitive information to us via electronic mail, including social
>security numbers, account numbers, or personal identification
>numbers. Delivery, and or timely delivery of Internet mail is not
>guaranteed. Western Asset therefore recommends that you do not send
>time sensitive or action-oriented messages to us via electronic
>mail. 
>**********************************************************************
>-------------- next part --------------
>An HTML attachment was scrubbed...
>-------------- next part --------------
>A non-text attachment was scrubbed...
>Name: SpringContextLoaderListener.java
>Type: application/octet-stream
>Size: 3098 bytes
>Desc: SpringContextLoaderListener.java
>
>------------------------------
>
>--------------------------------------------------------------------------
>----
>Precog is a next-generation analytics platform capable of advanced
>analytics on semi-structured data. The platform includes APIs for building
>apps and a phenomenal toolset for data science. Developers can use
>our toolset for easy data analysis & visualization. Get a free account!
>http://www2.precog.com/precogplatform/slashdotnewsletter
>
>------------------------------
>
>_______________________________________________
>Resteasy-developers mailing list
>Res...@li...
>https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>
>
>End of Resteasy-developers Digest, Vol 62, Issue 1
>**************************************************

Re: [Resteasy-developers] Programatically registering exception mappers

[Bill B. <bb...@re...>]

You can return them from Application class getClasses() and 
getSingletons() method.  This only happens at bootstrap though.

Also, you can inject a Configurable via @Context.  It should be 
threadsafe to call the register() methods of Configurable.

On 4/22/2013 7:23 AM, Michael McCarthy wrote:
> Hi all,
>
> I'm working on a project similar to Dropwizard but with a slightly
> different set of technologies specific to our company (RESTeasy instead
> of Jersey being one of the technology choices). Teams extend a framework
> class and all being well get a running servlet container with RESTeasy
> as the JAX-RS provider. All instantiation of RESTeasy is programatic.
>
> I want users of the framework to provide exceptions with status codes,
> and for the framework to add these programatically as ExceptionMapper
> classes. My intention was to override the RESTeasyBootstrap class and
> use the providerFactory from the deployment.
>
> It only seems that I can either add ClientExceptionMappers (which isn't
> what I want) or raw providers – is there are any reason I can't add an
> ExceptionMapper directly? I'll be constructing my ExceptionMapper on the
> fly based on the exceptions provided by the clients.
>
> Many thanks
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

Re: [Resteasy-developers] JAX-RS 2.0: Response doesn't implement Autoclosable

[Bill B. <bb...@re...>]

Compatibility with JDK 6.  Many of us have customers/users still on JDK 5!!!

On 4/22/2013 6:59 AM, Juergen Zimmermann wrote:
> Due to the spec javax.ws.rs.core.Response doesn't implement the
> interface Autoclosable (see Java SE 7). Does anyone know the reason for
> omitting Autoclosable?
>
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
>
>
>
> _______________________________________________
> Resteasy-developers mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-developers
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

[Resteasy-developers] Programatically registering exception mappers

[Michael M. <mic...@ga...>]

Hi all,

I'm working on a project similar to Dropwizard but with a slightly different set of technologies specific to our company (RESTeasy instead of Jersey being one of the technology choices). Teams extend a framework class and all being well get a running servlet container with RESTeasy as the JAX-RS provider. All instantiation of RESTeasy is programatic.

I want users of the framework to provide exceptions with status codes, and for the framework to add these programatically as ExceptionMapper classes. My intention was to override the RESTeasyBootstrap class and use the providerFactory from the deployment.

It only seems that I can either add ClientExceptionMappers (which isn't what I want) or raw providers – is there are any reason I can't add an ExceptionMapper directly? I'll be constructing my ExceptionMapper on the fly based on the exceptions provided by the clients.

Many thanks

[Resteasy-developers] JAX-RS 2.0: Response doesn't implement Autoclosable

[Juergen Z. <Jue...@HS...>]

Due to the spec javax.ws.rs.core.Response doesn't implement the interface
Autoclosable (see Java SE 7). Does anyone know the reason for omitting
Autoclosable?