Hi David...

The mail is not directed to me :), but I really want to join into these
tests specially the ones which their container code is not implemented yet
so I can write the test case and go through its related container code too
:), so I would like to have these ones:

[OPENEJB-160] iTest: StatelessBeanSetterInjectionTests
[OPENEJB-186] iTest: StatefulBeanSetterInjectionTests

On 11/15/06, David Blevins <[EMAIL PROTECTED]> wrote:

On Nov 9, 2006, at 6:10 AM, Manu George wrote:

> Hi David,
>               That explains it. The Pojo name in some of the test
> cases. I was wondering what it was. I have attached the patches for
> 152 and 156.

Ok, I've got 152 and 156 applied and checked in.  Thank you very much
for those!

> Please assign some others to me namely 154 and 155.

I see you already have these completed and patches in for those --
you work fast.  I'll get those in for you today too.

Thanks Manu!  You're really cruising these tests.  Any interest in
working on one of these?

    [OPENEJB-160] iTest: StatelessBeanSetterInjectionTests
    [OPENEJB-161] iTest: StatelessBeanPublicFieldInjectionTests
    [OPENEJB-162] iTest: StatelessBeanCallbackTests
    [OPENEJB-186] iTest: StatefulBeanSetterInjectionTests
    [OPENEJB-187] iTest: StatefulBeanPublicFieldInjectionTests
    [OPENEJB-188] iTest: StatefulBeanCallbackTests

Not as easy as the other ones as there's no pre-existing test to copy/
paste from.  But I get the feeling you may be up to the challenge.
The corresponding setter injection code in the container has not been
written, so these tests will not pass but they will be a very big
help in completing that functionality.

Thoughts?

-David




--
Thanks
- Mohammad Nour

Reply via email to