geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Created: (GERONIMO-393) Alter connector configuration for MDBs in openejb-jar.xml
Date Mon, 25 Oct 2004 02:08:25 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: GERONIMO-393
    Summary: Alter connector configuration for MDBs in openejb-jar.xml
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Apache Geronimo

   Assignee: David Jencks
   Reporter: Aaron Mulder

    Created: Sun, 24 Oct 2004 7:07 PM
    Updated: Sun, 24 Oct 2004 7:07 PM

It is not (ever) necessary to manually specify the activation-spec-class for a message driven
bean in openejb-jar.xml.

Once the resource adapter has been identified, the ActivationSpec must go with a particular
messagelistener-type.  The messaging-type is always configured for the MDB (if omitted from
ejb-jar.xml, it specifically defaults to javax.jms.MessageListener), and the messagelistener-type
must be unique in the inbound-resourceadapter (due to messagelistener-type-uniqueness).  Given
the resource adapter and messaging-type, the ActivationSpec is determined as well.

The resource adapter must still be specified in openejb-jar.xml unless the MDB uses a message-destination-link
in ejb-jar.xml (in which case the adminobject linked to identifies the resource adapter).
 Thus, the resource-adapter-name should be optional in openejb-jar.xml, and a runtime check
should be added that throws a deployment error if the resource adapter cannot be identified
(no resource-adapter-name in openejb-jar.xml and no message-destination-link in ejb-jar.xml)

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message