geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Closed: (GERONIMO-393) Alter connector configuration for MDBs in openejb-jar.xml
Date Thu, 28 Oct 2004 02:04:32 GMT
     [ ]
David Jencks closed GERONIMO-393:

     Resolution: Fixed
    Fix Version: 1.0-M3

The activation spec type is now deduced from the message listener type.  Since (per GERONIMO-372)
admin objects are no longer associated with a particular resource adapter instance, determining
the resource adapter from the admin object is no longer possible.

> Alter connector configuration for MDBs in openejb-jar.xml
> ---------------------------------------------------------
>          Key: GERONIMO-393
>          URL:
>      Project: Apache Geronimo
>         Type: Improvement
>   Components: connector
>     Versions: 1.0-M2
>     Reporter: Aaron Mulder
>     Assignee: David Jencks
>      Fix For: 1.0-M3

> 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