[jax-rs-spec users] [jsr339-experts] Re: Server sided use of JAX-RS client API: Valid in which server sided components?

From: Bill Burke <>
Date: Mon, 18 Jun 2012 10:23:59 -0400

Even if it was "forbidden" it certainly can't be enforced.
Historically, the problems with threading were there was no way to
propagate security/transactional contexts, I think this is changed now
that EJB has an async layer.

On 6/16/12 9:50 AM, Markus KARG wrote:
> Experts,
> some weeks ago we discussed server sided use of the new JAX-RS client
> API, e. g. to pull information from an external RESTful web service.
> As I remember, at least for EJBs (SBs, MDBs) it is forbidden to use
> blocking operations, threading operations, files API and sockets API.
> All this for the sake of stability and security. So the good question
> now is: Is this at least allowed for managed beans (CDI / JSF) or
> servlets? Anybody being a member of that particular EGs, knowing the
> answer for sure? Because if the same rule would apply to managed beans,
> JSF and servlets, what server side use case did we actually had in mind
> back then? RAR? JCA? Please comment. :-)
> Thanks
> Markus

Bill Burke
JBoss, a division of Red Hat