Hi David/Mohammad,

What I was planning was to add annotated beans for each of the
corressponding beans deployed using the deployment descriptor. Then
execute all the test cases existing for the dd deployed beans for the
annotated beans as well. In addition to this we need to create new
test cases for checking the overrides as well as the defaults(i.e.
beans with the very minimum annotations. The unpecified config
attributes should be substituted by defaults).
       I was thinking that if we can deploy the annotated ejbs with
the same name as the dd based ones we can execute the existing tests
as well. We will have the beans and remote interfaces extending from
the existing ones as well.
       I plan to implement this by creating two new TestSuites
corressponding to iTest and RemoteiTest namely AnnotatediTest and
AnnotatedRemoteiTest. In iTest and RemoteiTest I will add the
following system property
System.setProperty("openejb.deployments.classpath.exclude",
".*openejb-itests-annotated-beans.*");
This will prevent openejb from loading the descriptors in that
directory and so the annotated beans.Similarly if I set the property
to .*openejb-itests-beans.* in AnnotatediTests suite then the dd based
beans won't be deployed. This will minimize the tests we need to write
for annotated beans. One issue I am not sure of here is even though we
will have annotated business interfaces in the jar deployed in server
the existing tests will use the parent interfaces only so we may need
to create some tests with annotated interfaces used at client side.
        Now I may have been missing something when i came up with
this approach and so it may not work. So I am looking for your
comments poiniting out the issues with this approach. Better
ideas,improvements and comments are welcome from anyone.

Thanks
Manu

On 11/20/06, David Blevins <[EMAIL PROTECTED]> wrote:
On Nov 20, 2006, at 1:48 AM, Manu George wrote:

> Hi David,
>              Have you created the beans that we are going to test
> annotations? If not shall I go ahead and create the beans as extending
> from the current test beans. I plan to create the session beans
> required for testing the annotations you have implemented.

Go for it!

You can throw everything into an itests/openejb-itests-annotated-
beans/ module.

Note sure just yet how we'll wire it in to run with the other tests.
If you have any ideas, I'm all ears.

-David




Reply via email to