users@jersey.java.net

Re: [Jersey] Exposing EJB 3 Beans through JAX-RS

From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Mon, 08 Sep 2008 16:08:47 -0400

On Sep 8, 2008, at 3:21 PM, Reza Rahman wrote:
>
> I would definitely like to see a bit more flexibility than having to
> use WebBeans/believe there is a need for EJB 3.1/JAX-RS integration.
> How can I provide further input into the decision making process for
> this short of trying to join the JSR 311 EG? I can most certainly
> try to gauge/build support for this by blogging/talking about my own
> viewpoints if that is what could help.
>
IIUC, the goal of WebBeans is to unify the component model for the EJB
and Web containers. I can understand the desire for a point-wise
integration but it seems to me that supporting a unified model would
be more beneficial overall. E.g. a bean could then be used as a JAX-RS
resource class, a JSF managed bean and as an EJB session bean. I
haven't been following WebBeans closely so far but from what I've seen
there's very little work required to make an EJB session bean a WebBean.

Marc.

>
> Marc Hadley wrote:
>> On Sep 8, 2008, at 1:46 PM, Reza Rahman wrote:
>>>
>>> I'll be honest, I'd hate to see a potentially good technology like
>>> JAX-RS be out of the reach of developers that would rather use a
>>> plain EJB stack for reasons that are relatively easily solvable. I
>>> definitely do hope for much better coordination between specs in
>>> Java EE than that, particularly in the GlassFish project!
>>>
>> Sorting out integration with EE 6 is on the docket for JAX-RS 1.1,
>> a maintenance release we are planning to align with the EE 6
>> schedule. Exactly what this will look like is still up for debate
>> but the current thinking is outlined in section 6.2 of the spec (https://jsr311.dev.java.net/drafts/spec20080827.pdf
>> ).
>>
>> Personally I'd like to be able to say that a resource class can be
>> a WebBean and leave it at that - I think that would give you what
>> you are looking for. However, it remains to be seen if that will be
>> feasible or not.
>>
>> Marc.
>>
>> ---
>> Marc Hadley <marc.hadley at sun.com>
>> CTO Office, Sun Microsystems.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.