Paul,
* Interesting, do you have any pointers to that work?
- Not yet. I am still trying to get political buy-in from Rod
Johnson/SpringSource, which seems to be going better than I had ever
expected it to go. If that effort breaks down, I'll host it on Java.net
and start publicizing it sooner rather than later. I can certainly keep
you posted on it if you want. It should be fairly visible on its own
right, though...
* We plan to work on a maintenance release of JAX-RS that aligns with EE
6 and the technologies that are part of it. The discussions we have been
having so far have been most useful in helping to prepare for that :-)
any implementation work and examples will likely help drive what may be
specified.
- A bit more indirect from what I was hoping for, but fair enough :-).
I'll get the process bootstrapped and hand-off to one of the folks that
might be interested in committing code to the Jersey project...
Cheers,
Reza
Paul Sandoz wrote:
> Hi Reza,
>
>> OK, I'll try to see what time permits.
>
> Thanks!
>
>
>>
>> Speaking about this with a few friends real quick over IM,
>> implementation help is definitely possible (not necessarily from me
>> since I am currently busy trying to implement EJB 3.1 Lite for the
>> Spring framework/platform).
>
> Interesting, do you have any pointers to that work?
>
>
>> However, they and I would want to know the likelihood of EJB
>> 3.1/JAX-RS integration being standards defined/approved rather than
>> being implementation specific...
>> You being a co-spec lead on JSR 311, what's your thoughts on that?
>>
>
> We plan to work on a maintenance release of JAX-RS that aligns with EE
> 6 and the technologies that are part of it. The discussions we have
> been having so far have been most useful in helping to prepare for
> that :-) any implementation work and examples will likely help drive
> what may be specified.
>
> Paul.
>
>
>> Cheers,
>> Reza
>>
>>
>> Reza Rahman wrote:
>>> OK, I'll try to see what time permits.
>>>
>>> Paul Sandoz wrote:
>>>>
>>>> On Sep 8, 2008, at 6:25 PM, Reza Rahman wrote:
>>>>
>>>>> Paul,
>>>>>
>>>>> Great! I'm definitely interested to take a look...is there any
>>>>> specific help you need in terms of a sample?
>>>>>
>>>>
>>>> If it does not sounds too cheeky specific help could be to write
>>>> one that could be contributed back to the Jersey distribution :-)
>>>> it does not have to be complicated to get the point across on how
>>>> to use session EJBs with Jersey. Perhaps it would be a good way to
>>>> play with JAX-RS and understand more about how better to improve
>>>> EJB integration?
>>>>
>>>>
>>>>> I'd still be interested to fully hear out your thoughts on EJB 3.1
>>>>> support and try to help the best I can from an EG standpoint...I
>>>>> think it's very important to have great alignment between the EJB
>>>>> 3.1 and JAX-RS specs.
>>>>>
>>>>
>>>> I agree.
>>>>
>>>> Paul.
>>>>
>>>>> Cheers,
>>>>> Reza
>>>>>
>>>>>
>>>>> Paul Sandoz wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have just committed to the trunk support for session beans as
>>>>>> resource classes. You may have to wait a bit for it to propagate
>>>>>> to the trunk.
>>>>>>
>>>>>> To enable this you need to do the following:
>>>>>>
>>>>>> 1) use the Jersey servlet or an extension of (e.g. the spring
>>>>>> servlet);
>>>>>>
>>>>>> 2) annotate remote interfaces as root resource classes; and
>>>>>>
>>>>>> 3) configure Jersey such that the annotated remote interfaces in
>>>>>> 2) are registered as root resource classes. This
>>>>>> can be achieved using the package scanning technique and
>>>>>> referencing the package(s) where the remote
>>>>>> interfaces reside.
>>>>>>
>>>>>> Jersey will, if a registered root resource class is an interface
>>>>>> look up a JNDI named object using the fully qualified class name
>>>>>> as the JNDI name. If a named object exists then the root resource
>>>>>> class is removed from the set of registered root resource classes
>>>>>> and the named object is added to the singleton root resource
>>>>>> instances.
>>>>>>
>>>>>> I am sure this could be refined a little in terms of naming. I
>>>>>> have been using Glassfish v2 ur2 as shipped with NetBeans 6.5
>>>>>> beta. I dunno if the name scheme works with other app servers.
>>>>>>
>>>>>> Now we require a sample :-)
>>>>>>
>>>>>> Paul.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>>>>>> <mailto:users-unsubscribe_at_jersey.dev.java.net>
>>>>>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>>>>> <mailto:users-help_at_jersey.dev.java.net>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>>>> <mailto:users-unsubscribe_at_jersey.dev.java.net>
>>>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>>> <mailto:users-help_at_jersey.dev.java.net>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>>> <mailto:users-unsubscribe_at_jersey.dev.java.net>
>>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>> <mailto:users-help_at_jersey.dev.java.net>
>>>
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> <mailto:users-unsubscribe_at_jersey.dev.java.net>
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
> <mailto:users-help_at_jersey.dev.java.net>
>
>