@Resource.lookup

[Jarek Gawor <jg...@gmail.com>]

Hi,

I can't really find a reference to it in the EJB 3.1 spec, but I'm
pretty sure EJB 3.1 needs to support the @Resource annotation from the
Common Annotations 1.1 spec. One of the new things in 1.1 spec is the
'lookup' attribute on the Resource annotation. OpenEJB will need to
recognize & support that attribute. Here's one problem: Java 6
provides Common Annotation 1.0 classes. So in order to support
@Resource.lookup attribute we will need to 1) use reflection to get
the 'lookup' attribute value OR 2) configure the compiler, surefire,
etc. maven plugins to execute with appropriate java.endorsed.dirs
settings so that right version of Common Annotation is used.

I'm wondering which solution is a preferred solution. #1 seems much
easier. Also, if we go with #2 then deploying OpenEJB in e.g. Tomcat
might be a bit more difficult since the JVM will also need to be
configured to use the right annotation spec.

Thoughts?

Jarek

Re: @Resource.lookup

[David Blevins <da...@visi.com>]

On Aug 9, 2010, at 2:01 PM, David Blevins wrote:

> The mantra as always; be as invisible as possible.

Maybe to add a bit more context.  In embedded mode, we currently do not require:

  1. Files or Directories:  No configuration or logging files or anything are required for startup or usage.  We will readily create all needed containers, resources etc. from default settings (which are different for embedded mode).  HSQLDB is setup using the in memory DB.
  2. Ports: We don't consume any ports in embedded mode, so no port conflicts can occur.  @Remote EJB calls and MDBs all work over their "local" transports (one of the critical things we do with the different embedded settings).
  3. Java Agent: Avoidable if not using no JPA at all, Hibernate, and limited OpenJPA usage.
  4. ClassLoaders: we use what you created us in.

Probably more to add that list, but those are some of the basics.  Definitely a bit of work to maintain that level of invisibility, but that's the value add.

Come to think of it, might be good to add that to the docs somewhere.


-David

Re: @Resource.lookup

[David Blevins <da...@visi.com>]

On Aug 9, 2010, at 12:52 PM, Jarek Gawor wrote:

> It is. But I think OpenEJB is a bit different since it can be deployed
> in different environments, e.g. Tomcat. If we go #2 it would require a
> bit more configuration from the user to get OpenEJB running. It
> wouldn't be as easy as it is now.
> In Geronimo we control everything so #2 works fine for us.

Right, #1 would be more consistent on how OpenEJB tackles this kind of thing.  On a similar note, we don't require a Java Agent either.  Any serious usage of course should involve a javaagent if OpenJPA is the provider, but we don't require it to kick the tires.

The mantra as always; be as invisible as possible.


-David


> On Mon, Aug 9, 2010 at 3:43 PM, David Jencks <da...@yahoo.com> wrote:
>> I'd prefer #2.  Isn't this what we do in geronimo?
>> 
>> thanks
>> david jencks
>> 
>> On Aug 9, 2010, at 11:52 AM, Jarek Gawor wrote:
>> 
>>> Hi,
>>> 
>>> I can't really find a reference to it in the EJB 3.1 spec, but I'm
>>> pretty sure EJB 3.1 needs to support the @Resource annotation from the
>>> Common Annotations 1.1 spec. One of the new things in 1.1 spec is the
>>> 'lookup' attribute on the Resource annotation. OpenEJB will need to
>>> recognize & support that attribute. Here's one problem: Java 6
>>> provides Common Annotation 1.0 classes. So in order to support
>>> @Resource.lookup attribute we will need to 1) use reflection to get
>>> the 'lookup' attribute value OR 2) configure the compiler, surefire,
>>> etc. maven plugins to execute with appropriate java.endorsed.dirs
>>> settings so that right version of Common Annotation is used.
>>> 
>>> I'm wondering which solution is a preferred solution. #1 seems much
>>> easier. Also, if we go with #2 then deploying OpenEJB in e.g. Tomcat
>>> might be a bit more difficult since the JVM will also need to be
>>> configured to use the right annotation spec.
>>> 
>>> Thoughts?
>>> 
>>> Jarek
>> 
>> 
> 

Re: @Resource.lookup

[Jarek Gawor <jg...@gmail.com>]

It is. But I think OpenEJB is a bit different since it can be deployed
in different environments, e.g. Tomcat. If we go #2 it would require a
bit more configuration from the user to get OpenEJB running. It
wouldn't be as easy as it is now.
In Geronimo we control everything so #2 works fine for us.

Jarek

On Mon, Aug 9, 2010 at 3:43 PM, David Jencks <da...@yahoo.com> wrote:
> I'd prefer #2.  Isn't this what we do in geronimo?
>
> thanks
> david jencks
>
> On Aug 9, 2010, at 11:52 AM, Jarek Gawor wrote:
>
>> Hi,
>>
>> I can't really find a reference to it in the EJB 3.1 spec, but I'm
>> pretty sure EJB 3.1 needs to support the @Resource annotation from the
>> Common Annotations 1.1 spec. One of the new things in 1.1 spec is the
>> 'lookup' attribute on the Resource annotation. OpenEJB will need to
>> recognize & support that attribute. Here's one problem: Java 6
>> provides Common Annotation 1.0 classes. So in order to support
>> @Resource.lookup attribute we will need to 1) use reflection to get
>> the 'lookup' attribute value OR 2) configure the compiler, surefire,
>> etc. maven plugins to execute with appropriate java.endorsed.dirs
>> settings so that right version of Common Annotation is used.
>>
>> I'm wondering which solution is a preferred solution. #1 seems much
>> easier. Also, if we go with #2 then deploying OpenEJB in e.g. Tomcat
>> might be a bit more difficult since the JVM will also need to be
>> configured to use the right annotation spec.
>>
>> Thoughts?
>>
>> Jarek
>
>

Re: @Resource.lookup

[David Jencks <da...@yahoo.com>]

I'd prefer #2.  Isn't this what we do in geronimo?

thanks
david jencks

On Aug 9, 2010, at 11:52 AM, Jarek Gawor wrote:

> Hi,
> 
> I can't really find a reference to it in the EJB 3.1 spec, but I'm
> pretty sure EJB 3.1 needs to support the @Resource annotation from the
> Common Annotations 1.1 spec. One of the new things in 1.1 spec is the
> 'lookup' attribute on the Resource annotation. OpenEJB will need to
> recognize & support that attribute. Here's one problem: Java 6
> provides Common Annotation 1.0 classes. So in order to support
> @Resource.lookup attribute we will need to 1) use reflection to get
> the 'lookup' attribute value OR 2) configure the compiler, surefire,
> etc. maven plugins to execute with appropriate java.endorsed.dirs
> settings so that right version of Common Annotation is used.
> 
> I'm wondering which solution is a preferred solution. #1 seems much
> easier. Also, if we go with #2 then deploying OpenEJB in e.g. Tomcat
> might be a bit more difficult since the JVM will also need to be
> configured to use the right annotation spec.
> 
> Thoughts?
> 
> Jarek