You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Dave Colasurdo <da...@earthlink.net> on 2007/01/25 20:03:23 UTC

Release Notes for 2.0-M2 - EJB content

I'm helping Hernan update the Release Notes for 2.0-M2.

Can folks please provide feedback for the EJB Content that gets 
documented in the Release Notes.

Here is the current content..

- EJB 3.0 (via OpenEJB project)
    Supported:
       - JPA (Custom Provider, App-managed, Container-managed) (Also 
supported in 2.0-M1)
       - POJO as a Business Interface (both local and remote)
       - POJO Session EJBs
       - Deployment with no ejb-jar.xml or openejb-jar (just need a 
geronimo-openejb.xml for all the geronimo-specific deployment stuff)
       - Deployment of annotated beans (@Stateful and @Stateless)
       - Injection via deployment descriptor
        - @Resource injection for env-entries, resource-refs, 
message-destinations, service-refs,  most resource-env-refs
        - @EJB injection of ejb-refs and ejb-local-refs
        - @PersistenceContext injection
        - @PersistenceUnit injection
       - JNDI references to the ejb
       - JNDI references from the ejb
       - Transaction support
       - Legacy component (i.e. home) interfaces on a Pojo session bean
       - Xml-based *and* annotation-based injection for ejbs, except for 
message-destinations,
         or SessionContext when the field or setter is not named 
setSessionContext
       - References to business interfaces, local or remote, from a 
servlet or an ejb
       - References to home interfaces, local or remote, from a servlet 
or an ejb

    Limitations:
       - Extended JNDI and DI types
       - Undeploying an ejb module will not remove it's beans. The 
server has to be restarted to deploy the same module again.

Thanks
-Dave-

Re: Release Notes for 2.0-M2 - EJB content

Posted by Dave Colasurdo <da...@earthlink.net>.
Ok, have clarified this in the release notes..

Thanks
-Dave-

Dain Sundstrom wrote:
> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
> 
>> - Deployment with no ejb-jar.xml or openejb-jar (just need a 
>> geronimo-openejb.xml for all the geronimo-specific deployment stuff)
> 
> To be clear, the geronimo-openejb.xml file is only required if you have 
> some geronimo specific stuff that must be configured.  In general you 
> don't need one.
> 
> -dain
> 
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by Dain Sundstrom <da...@iq80.com>.
On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:

> - Deployment with no ejb-jar.xml or openejb-jar (just need a  
> geronimo-openejb.xml for all the geronimo-specific deployment stuff)

To be clear, the geronimo-openejb.xml file is only required if you  
have some geronimo specific stuff that must be configured.  In  
general you don't need one.

-dain

Re: Release Notes for 2.0-M2 - EJB content

Posted by Joe Bohn <jo...@earthlink.net>.
David,

Did this change make it into the 2.0-M2 branch and the image that Matt 
is creating for a vote?

Joe


David Blevins wrote:
> 
> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
> 
>>    Limitations:
>>       - Undeploying an ejb module will not remove it's beans. The 
>> server has to be restarted to deploy the same module again.
> 
> Ok, I've implemented undeploy and verified it works using the calculator 
> sample app.  I can guarantee there are leaks here (there always are the 
> first few iterations), but the feature is functional.
> 
>>       - Extended JNDI and DI types
> 
> This works.  If your env-entry-type is java.lang.String and we see you 
> have a URL, for example, we will convert the value to a URL before 
> injection.
> 
> -David
> 
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by David Blevins <da...@visi.com>.
On Jan 26, 2007, at 12:21 PM, Bill Stoddard wrote:

> David Blevins wrote:
>>
>> On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:
>>
>>> Thanks... Have made the updates...
>>>
>>> Is there anything that should be added to the limitations section?
>>
>> One of the things I mentioned in another email is that MDBs are  
>> completely untested and should be assumed non-functional.
>>
>>>   Do we fully support EJB 3.0?
>>
>> :)
>>
>> -David
>
> The answer probably depends on the definition of 'fully'. :)

LOL!

-David

Re: Release Notes for 2.0-M2 - EJB content

Posted by Bill Stoddard <bi...@wstoddard.com>.
David Blevins wrote:
>
> On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:
>
>> Thanks... Have made the updates...
>>
>> Is there anything that should be added to the limitations section?
>
> One of the things I mentioned in another email is that MDBs are 
> completely untested and should be assumed non-functional.
>
>>   Do we fully support EJB 3.0?
>
> :)
>
> -David

The answer probably depends on the definition of 'fully'. :)

Bill

Re: Release Notes for 2.0-M2 - EJB content

Posted by Prasad Kashyap <go...@gmail.com>.
On 1/26/07, Dave Colasurdo <da...@earthlink.net> wrote:
> Thanks... Have included the MDB restriction in the latest attachment.
>
> BTW, The version in the 2.0-M2 branch is quite stale.
>
> Can someone please refresh the copy at:
> https://svn.apache.org/repos/asf/geronimo/server/branches/2.0-M2/RELEASE-NOTES-2.0-M2.TXT
>
> with the included attachment.

Done

>
> All future changes can then occur in the branch..
>
> Thanks
> -Dave-

Cheers
Prasad

Re: Release Notes for 2.0-M2 - EJB content

Posted by Dave Colasurdo <da...@earthlink.net>.
Thanks... Have included the MDB restriction in the latest attachment.

BTW, The version in the 2.0-M2 branch is quite stale.

Can someone please refresh the copy at: 
https://svn.apache.org/repos/asf/geronimo/server/branches/2.0-M2/RELEASE-NOTES-2.0-M2.TXT

with the included attachment.

All future changes can then occur in the branch..

Thanks
-Dave-

David Blevins wrote:
> 
> On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:
> 
>> Thanks... Have made the updates...
>>
>> Is there anything that should be added to the limitations section?
> 
> One of the things I mentioned in another email is that MDBs are 
> completely untested and should be assumed non-functional.
> 
>>   Do we fully support EJB 3.0?
> 
> :)
> 
> -David
> 
> 
>>
>> -Dave-
>>
>> David Blevins wrote:
>>> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
>>>>    Limitations:
>>>>       - Undeploying an ejb module will not remove it's beans. The 
>>>> server has to be restarted to deploy the same module again.
>>> Ok, I've implemented undeploy and verified it works using the 
>>> calculator sample app.  I can guarantee there are leaks here (there 
>>> always are the first few iterations), but the feature is functional.
>>>>       - Extended JNDI and DI types
>>> This works.  If your env-entry-type is java.lang.String and we see 
>>> you have a URL, for example, we will convert the value to a URL 
>>> before injection.
>>> -David
>>
> 
> 
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by David Blevins <da...@visi.com>.
On Jan 26, 2007, at 5:46 AM, Dave Colasurdo wrote:

> Thanks... Have made the updates...
>
> Is there anything that should be added to the limitations section?

One of the things I mentioned in another email is that MDBs are  
completely untested and should be assumed non-functional.

>   Do we fully support EJB 3.0?

:)

-David


>
> -Dave-
>
> David Blevins wrote:
>> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
>>>    Limitations:
>>>       - Undeploying an ejb module will not remove it's beans. The  
>>> server has to be restarted to deploy the same module again.
>> Ok, I've implemented undeploy and verified it works using the  
>> calculator sample app.  I can guarantee there are leaks here  
>> (there always are the first few iterations), but the feature is  
>> functional.
>>>       - Extended JNDI and DI types
>> This works.  If your env-entry-type is java.lang.String and we see  
>> you have a URL, for example, we will convert the value to a URL  
>> before injection.
>> -David
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by Dave Colasurdo <da...@earthlink.net>.
Ok, have added back the restriction regarding undeploying ejb modules 
for 2.0-M2.  Attaching the latest release notes to this email.  Please 
verify the eol characters are in the correct format..

Matt will add the Release Notes to the official build.

-Dave-

Prasad Kashyap wrote:
> Two issues here -
> 
> 1) Dain's fixes are in trunk. They have not been merged with the M2
> changes yet. So at the moment, the M2 has these limitations.
> 
> 2) This is a bigger issue. I don't see the Release Notes in the
> unpacked server !!!
> 
> Cheers
> Prasad
> 
> On 1/26/07, Kevan Miller <ke...@gmail.com> wrote:
>>
>> On Jan 26, 2007, at 8:46 AM, Dave Colasurdo wrote:
>>
>> > Thanks... Have made the updates...
>>
>> Well, we need to be sure these changes are included in M2. I'm not
>> sure where Matt is in terms of building an RC.
>>
>> --kevan
>>
>> >
>> > Is there anything that should be added to the limitations section?
>> > Do we fully support EJB 3.0?
>> >
>> > -Dave-
>> >
>> > David Blevins wrote:
>> >> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
>> >>>    Limitations:
>> >>>       - Undeploying an ejb module will not remove it's beans. The
>> >>> server has to be restarted to deploy the same module again.
>> >> Ok, I've implemented undeploy and verified it works using the
>> >> calculator sample app.  I can guarantee there are leaks here
>> >> (there always are the first few iterations), but the feature is
>> >> functional.
>> >>>       - Extended JNDI and DI types
>> >> This works.  If your env-entry-type is java.lang.String and we see
>> >> you have a URL, for example, we will convert the value to a URL
>> >> before injection.
>> >> -David
>>
>>
> 
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by Prasad Kashyap <go...@gmail.com>.
Two issues here -

1) Dain's fixes are in trunk. They have not been merged with the M2
changes yet. So at the moment, the M2 has these limitations.

2) This is a bigger issue. I don't see the Release Notes in the
unpacked server !!!

Cheers
Prasad

On 1/26/07, Kevan Miller <ke...@gmail.com> wrote:
>
> On Jan 26, 2007, at 8:46 AM, Dave Colasurdo wrote:
>
> > Thanks... Have made the updates...
>
> Well, we need to be sure these changes are included in M2. I'm not
> sure where Matt is in terms of building an RC.
>
> --kevan
>
> >
> > Is there anything that should be added to the limitations section?
> > Do we fully support EJB 3.0?
> >
> > -Dave-
> >
> > David Blevins wrote:
> >> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
> >>>    Limitations:
> >>>       - Undeploying an ejb module will not remove it's beans. The
> >>> server has to be restarted to deploy the same module again.
> >> Ok, I've implemented undeploy and verified it works using the
> >> calculator sample app.  I can guarantee there are leaks here
> >> (there always are the first few iterations), but the feature is
> >> functional.
> >>>       - Extended JNDI and DI types
> >> This works.  If your env-entry-type is java.lang.String and we see
> >> you have a URL, for example, we will convert the value to a URL
> >> before injection.
> >> -David
>
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by Kevan Miller <ke...@gmail.com>.
On Jan 26, 2007, at 8:46 AM, Dave Colasurdo wrote:

> Thanks... Have made the updates...

Well, we need to be sure these changes are included in M2. I'm not  
sure where Matt is in terms of building an RC.

--kevan

>
> Is there anything that should be added to the limitations section?   
> Do we fully support EJB 3.0?
>
> -Dave-
>
> David Blevins wrote:
>> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
>>>    Limitations:
>>>       - Undeploying an ejb module will not remove it's beans. The  
>>> server has to be restarted to deploy the same module again.
>> Ok, I've implemented undeploy and verified it works using the  
>> calculator sample app.  I can guarantee there are leaks here  
>> (there always are the first few iterations), but the feature is  
>> functional.
>>>       - Extended JNDI and DI types
>> This works.  If your env-entry-type is java.lang.String and we see  
>> you have a URL, for example, we will convert the value to a URL  
>> before injection.
>> -David

Re: Release Notes for 2.0-M2 - EJB content

Posted by Dave Colasurdo <da...@earthlink.net>.
Thanks... Have made the updates...

Is there anything that should be added to the limitations section?  Do 
we fully support EJB 3.0?

-Dave-

David Blevins wrote:
> 
> On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:
> 
>>    Limitations:
>>       - Undeploying an ejb module will not remove it's beans. The 
>> server has to be restarted to deploy the same module again.
> 
> Ok, I've implemented undeploy and verified it works using the calculator 
> sample app.  I can guarantee there are leaks here (there always are the 
> first few iterations), but the feature is functional.
> 
>>       - Extended JNDI and DI types
> 
> This works.  If your env-entry-type is java.lang.String and we see you 
> have a URL, for example, we will convert the value to a URL before 
> injection.
> 
> -David
> 
> 
>

Re: Release Notes for 2.0-M2 - EJB content

Posted by David Blevins <da...@visi.com>.
On Jan 25, 2007, at 11:03 AM, Dave Colasurdo wrote:

>    Limitations:
>       - Undeploying an ejb module will not remove it's beans. The  
> server has to be restarted to deploy the same module again.

Ok, I've implemented undeploy and verified it works using the  
calculator sample app.  I can guarantee there are leaks here (there  
always are the first few iterations), but the feature is functional.

>       - Extended JNDI and DI types

This works.  If your env-entry-type is java.lang.String and we see  
you have a URL, for example, we will convert the value to a URL  
before injection.

-David